Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with database table (nametab) runtime object doesn't exists

Former Member
0 Kudos

Hi all !

Let mi quickly describe this problem.

All the screenshots and excel sheet are in [luxcar.com.pl/tomek/attachment.zip] - no viruses inside - I Promise !!

So problem is:

When I imported our package I got the problem with TWC table. Now, situation looks like this. When I import this table (I prepared the transport) to customers dev system (have SAP_ALL there), everything goes well u2013 no errors. When I run our solution, it crashes on /../TWC and says it doesnu2019t exist. When I access se80 and display /.../TWC properties, everything looks ok (see twc1.gif) u2013 system says that itu2019s active but doesnu2019t exist in database. Ok, I run database utility and press u201CCreate in databaseu201D . This ends up with error message (see twc2.gif). Itu2019s something about missing runtime object (nametab). When I come back to SE80 and press u201CActivateu201D , activation finishes with error log (see attached XLS file) and table turns into u201CPartly activeu201D (see twc3.gif).

We have another table /.../TWCV to store versions - it has EXACTLY the same structure as TWC but in opposite to TWC - there is no problem with transports, creation and activation. (It means - table structure is not a problem itself).

I tried recreating this table manually u2013 from the scratch. The same things happened. I thought it was something wrong with TADIR u2013 I checked and everything was ok there.

Can you help me?

Thank you in advance.

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

I did have a quick look at all your attachments and based on the error message & SQL script, I can see the table was created partly in DB. Because of it, if you try to delete it (drop table) and recreate it with your data, hopefully it should work.

As you can see, the SQL hasn't been completed. If its still doesn't work, then goto DB utility and do force coversion.

SQL: CREATE TABLE '/COCKPIT/TWC'

('CLIENT' VARCHAR (000003) NOT NULL DEFAUL '000' ,

'INVOICE_GUID' VARCHAR (000032) NOT NULL D ' ' ,

'WC_NO' VARCHAR (000003) NOT NULL DEFAULT '000' ,

'WC_VERSION' VARCHAR (000006) NOT NULL DEF '000000' ,

'VERSION' VARCHAR (000006) NOT NULL DEFAUL '000000' ,

'DOC_STATUS' VARCHAR (000002) NOT NULL DEF ' ' ,

'WC_ID' VARCHAR (000010) NOT NULL DEFAULT ' ' ,

'WC_DUEDATE' VARCHAR (000008) NOT NULL DEF '00000000' ,

'WC_STATUS' VARCHAR (000002) NOT NULL DEFA ' ' ,

'WC_POS' VARCHAR (000003) NOT NULL DEFAULT '000' ,

'WC_CH_TIMESTAMP' DECIMAL (000021, 000007) 0 ,

'ARCHIVED' VARCHAR (000001) NOT NULL DEFAU ' '

)

IN ________.________

Thanks

Ramesh

2 REPLIES 2

Former Member
0 Kudos

Hi,

I did have a quick look at all your attachments and based on the error message & SQL script, I can see the table was created partly in DB. Because of it, if you try to delete it (drop table) and recreate it with your data, hopefully it should work.

As you can see, the SQL hasn't been completed. If its still doesn't work, then goto DB utility and do force coversion.

SQL: CREATE TABLE '/COCKPIT/TWC'

('CLIENT' VARCHAR (000003) NOT NULL DEFAUL '000' ,

'INVOICE_GUID' VARCHAR (000032) NOT NULL D ' ' ,

'WC_NO' VARCHAR (000003) NOT NULL DEFAULT '000' ,

'WC_VERSION' VARCHAR (000006) NOT NULL DEF '000000' ,

'VERSION' VARCHAR (000006) NOT NULL DEFAUL '000000' ,

'DOC_STATUS' VARCHAR (000002) NOT NULL DEF ' ' ,

'WC_ID' VARCHAR (000010) NOT NULL DEFAULT ' ' ,

'WC_DUEDATE' VARCHAR (000008) NOT NULL DEF '00000000' ,

'WC_STATUS' VARCHAR (000002) NOT NULL DEFA ' ' ,

'WC_POS' VARCHAR (000003) NOT NULL DEFAULT '000' ,

'WC_CH_TIMESTAMP' DECIMAL (000021, 000007) 0 ,

'ARCHIVED' VARCHAR (000001) NOT NULL DEFAU ' '

)

IN ________.________

Thanks

Ramesh

Former Member
0 Kudos

It's a problem of DB2 old release incompatibility and restrictions.

There are two ways to solve this

- Change DB table name to longer

- Change DB table size category to lower