This looks like the same problem I ran into recently. One of your column
names is an Allbase reserved word. Here's the relevant section of the
explanation I got from HP Support. Hope this helps.
A SELECT of a column where the column name is an ALLBASE reserved word
will
fail, usually with a syntax error, DBERR 1001. This can be avoided by
using
a table prefix e.g.:
SELECT position FROM mytable; * Fails with DBERR 1001
SELECT a.position FROM mytable a; * Succeeds
The same situation applies when an embedded SELECT is used e.g.
CREATE VIEW myview AS SELECT position FROM....etc
IMAGESQL may create views during ATTACH, ADD USER, UPDATE USER, UPDATE
TYPE
and SPLIT. No table prefix is used, so creating a VIEW from a TurboIMAGE
dataset, where an item name is an ALLBASE reserved word will cause the
command to fail.
ALLBASE/SQL CREATE VIEW command failed (ATCERR 32357).
Syntax error. (DBERR 1001)
If the database has been successfully ATTACHed the problem item can be
renamed using SPLIT as a workaround e.g.
SPLIT mytable.position into newpositionname:X20
where X20 is the full size of the data item
VIEWs are also created for class 0 at ATTACH time, if class 0 has WRITE
access a set. So a VIEW is created for a set where no security is
specified
in the schema e.g.
Name: MYSET , master ;
or, where class 0 has write access e.g.
Name: MYSET ,master (/0,10);
If an ATTACH fails with ATCERR 32357, DBERR 1001, the way around this is
to
change the security definition for the set containing the problem data
item
name, to avoid class 0 having write access. That way no VIEWs are created
during the ATTACH.
----------
I have these 2 datasets:
Name: SCREEN-TABLE , Manual (10,20/20);
Entry:
SCREEN-NAME (0), << X16 >>
FUNCTION-LINE1 , << 8X8 >>
FUNCTION-LINE2 , << 8X8 >>
FUNCTION-KEY , << 8X4 >>
SCREEN-ID ; << X4 >>
Name: REPORT-MASTER , Manual (10,20/20);
Entry:
REPORT-NAME (0), << X16 >>
REPORT-NUMBER , << X4 >>
FORMS-MSG , << X30 >>
REPORT-TITLE , << X40 >>
JOB-PRIORITY , << X2 >>
PRINT-PRIORITY , << X2 >>
PRINT-COPIES , << X2 >>
OUTPUT-DEVICE , << X8 >>
RPT-SELECT1 , << X18 >>
RPT-SELECT2 , << X18 >>
RPT-SELECT3 , << X18 >>
COMMAND-FILE , << X8 >>
PROGRAM-NAME , << X8 >>
REMOTE-ID , << X8 >>
OUTPUT-TYPE ; << X8 >>
(Schema produced with ADAGER inorder to check for any "funny" field
security)
As MGR.AIMS, well, here is the script....
Xenon 32:IMAGESQL
HP36385B B.G4.02 IMAGE/SQL Utility TUE, AUG 8, 2000,
3:28
PM
(C) COPYRIGHT HEWLETT-PACKARD COMPANY 1993
>>SET DBE PURDBE
>>SET BASE ENGLSH
>>DI USER
ATTACHED BASES : ENGLSH.PUB.AIMS
DBEnvironment : PURDBE.PUB.AIMS
Owner Name : ENGLSH
USER LOGON DBOPEN MODE USER PASSWORD USER CLASS
---------- ----------- ------------- ----------
MGR.AIMS 5 ; 64
PURCH.AIMS 5 ; 64
>>UPDATE USER PURCH TO CLASS = 10
ALLBASE/SQL group ENGLSH_10 created.
View ENGLSH.MESSAGE_V10 created.
View ENGLSH.SCREEN_TABLE_V10 created.
ALLBASE/SQL CREATE VIEW command failed (ATCERR 32357).
Syntax error. (DBERR 1001)
>>
This error (ATCERR 32357) says
32357 MESSAGE ALLBASE/SQL CREATE VIEW command failed (ATCERR
32357).
CAUSE A preprocessed CREATE VIEW failed.
ACTION This message is followed by an ALLBASE/SQL error
message. Refer to the ALLBASE/SQL Message Manual
for more information.
And I find no reference in ALLBASE/SQL Message Manual (I only searched
for
32357.
Any ideas why this error and how to fix?
Doing this for other bases (same user) works ok.
> _____________________________________________________________
> Keven Miller mailto:[log in to unmask] http://www.exegesys.com
>
**********
Posted from www.3kworld.com
|
