Hi All,

This one's been bugging me a lot.

I just exported a package out of our Dev environment and imported to another Test Environment.
One of the tables is not created and gives error 512 from the GTM to allocate table.
There are no error messages when I do the create runtimes.

Here is what I found in the $BSE/log.


[TEST:nprao]/app/baan/bse/log >view log.oracle8

2002-09-04[17:34:16(UTC+08:00)]:E:bsp: ******* S T A R T of Error message *******
2002-09-04[17:34:16(UTC+08:00)]:E:bsp: Log message called from
/port.7.3a/vobs/tt/servers/ORACLE_2/ora_native.c: #2106 keyword: Oracle Error
2002-09-04[17:34:16(UTC+08:00)]:E:bsp: Pid 23326 Uid 125 Euid 125 Gid 125 Egid 125
Pset prnujetti@MBN273282:1148
2002-09-04[17:34:16(UTC+08:00)]:E:bsp: user_type S language 2 user_name bsp ttyote
locale ISO88591/NULL
2002-09-04[17:34:16(UTC+08:00)]:E:bsp: Errno 0 bdb_errno 110 (End of file reached)
2002-09-04[17:34:16(UTC+08:00)]:E:bsp:
2002-09-04[17:34:16(UTC+08:00)]:E:bsp: dbs_errno = 0Error 0 occurred:
2002-09-04[17:34:16(UTC+08:00)]:E:bsp: Error ORA-904 occurred during execute.
2002-09-04[17:34:16(UTC+08:00)]:E:bsp: ORA-00904: invalid column name
2002-09-04[17:34:16(UTC+08:00)]:E:bsp:
2002-09-04[17:34:16(UTC+08:00)]:E:bsp: Error BDB-512 returned.
2002-09-04[17:34:16(UTC+08:00)]:E:bsp: DD incompatible with table.
2002-09-04[17:34:16(UTC+08:00)]:E:bsp: See fatal SQL statement in
'/app/baan/bse/log /log.ora.sql'.
2002-09-04[17:34:16(UTC+08:00)]:E:bsp: Flushed at
/port.7.3a/vobs/tt/servers/ORACLE_2/ora_native.c : #2180.
2002-09-04[17:34:16(UTC+08:00)]:E:bsp: ******* E N D of Error message *******

[TEST:nprao]/app/baan/bse/log >vi log.ora.sql
------ Log Fatal SQL Statement -----
User : bsp (pid 23326)
Date : 2002-09-04[17:34:16]
SQL :
SELECT /*+ FIRST_ROWS INDEX(a0 tzmmig100100$idx1) */ a0.t$reqid,a0.t$reby,a0.t$proj,
a0.t$dfid,a0.t$stat,a0.t$pkg,a0.t$lang$1,a0.t$lang$2,a0.t$lang$3,a0.t$lang$4,
a0.t$lang$5,a0.t$ver_src,a0.t$ver_tar,a0.t$rls_src,a0.t$rls_tar,
a0.t$cust_src,a0.t$cust_tar,a0.t$mach_src,a0.t$mach_tar,a0.t$sblg,
a0.t$sbdt,a0.t$dvlg,a0.t$dvdt,a0.t$qalg,a0.t$qadt,a0.t$mqlg,a0.t$mqdt,
a0.t$prlg,a0.t$prdt,a0.t$mpdt,a0.t$mplg,a0.t$notes,a0.t$prslnks,a0.t$overwrit,
a0.t$cpyobj,a0.t$redt,a0.t$enby,a0.t$note,a0.t$fromcomp,a0.t$tocomp,a0.t$exchsch,
a0.t$exchdesc,a0.t$exchprog,a0.t$deflfile,a0.t$pathafil,a0.t$pathdfil,a0.t$bdlid,
a0.t$tdadt,a0.t$tdalg,a0.t$reqdesc,a0.t$rejlg,a0.t$rejdt,a0.t$esttime,a0.t$exchactn
FROM baan.tzmmig100100 a0 WHERE (a0.t$reqid >= :1) ORDER BY 1
------ End of Log Message -----


I couldnt figure out the context of -


2002-09-04[17:34:16(UTC+08:00)]:E:bsp: ORA-00904: invalid column name
2002-09-04[17:34:16(UTC+08:00)]:E:bsp: DD incompatible with table.

The table works fine and is created in the companies on Dev but not on the Test environment.

Any clues and tips are appreciated.

Thanks!

If you are running 8i, there is a possibility that Oracle is not properly patched.

try rerunning the catalog.sql script in the rdbms/admin directory.

NP -
Darn those 512's!
Seems like the convert / create did not take? Does the definition in Oracle match the definition in that SQL statement?
Is the package not existing already in Test..and is everything else all right with the package?
Try copying the definition in Test to another table name and convert dd - is everything ok?

Lisa,

Yes the messy 512's are back again... :eek:

I changed my package combination. I copied that table to the higher VRC, did a create runtime, no errors, logged out and logged back in, used GTM, and created table successfully.

Now when I go back to the original package combination, do runtime and try to create the table again for the company attached to that package combination the 512 is back again. :(

As Lisa, suggested, I copied the table to another table name, made runtime, logout & logback in and it still gives 512 error while creating the table.

As Francesco gave a tip, I am suspecting something to do the company/database setups/creations; I might need to hunt down our Oracle DBA guys.

Probably correct. There is 1 more piece of information to arm yourself with. Can you create a simple table in that environment at all? That would tell if it is related to that table specifically or environment related. If you cannot, you need to look to your setup as suggested. If you can, try building up to the table in question 1 field at a time, to find out where the problem is.

Lisa,

Its wierd all the other tables in that package except this one are successfully created... :confused:

I am getting the Oracle-DBA's to do something.

This is crazy... we just deleted the table and created it and it suddenly works.... sometimes its just wierd...!!! I cant explain what fixed it, the DBA's say they didnt do a thing.

oh well... whatever!!! the problem is solved. :D

Thanks Francesco and Lisa for sharing thoughts on this messy problem.