Waning in test, abort in prod
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 108
- Joined: Sat Feb 05, 2005 6:52 pm
- Location: US
Waning in test, abort in prod
Hi All,
When I run a job in test box I get the following message as warning but the job runs successfully where as I get the same message in the prod box the job aborts, can anybody tell me what needs to be done. I am usng DB2 plugin stage.
Error Message:
[IBM][CLI Driver][DB2] SQL0471N Invocation of routine "SYSIBM .SQLTABLES " failed due to reason "00E7900C". SQLSTATE=55023
SQLTables: Error retrieving system catalog information for requested tables(s).
Thanks,
Abhi.
When I run a job in test box I get the following message as warning but the job runs successfully where as I get the same message in the prod box the job aborts, can anybody tell me what needs to be done. I am usng DB2 plugin stage.
Error Message:
[IBM][CLI Driver][DB2] SQL0471N Invocation of routine "SYSIBM .SQLTABLES " failed due to reason "00E7900C". SQLSTATE=55023
SQLTables: Error retrieving system catalog information for requested tables(s).
Thanks,
Abhi.
Hi,
The most probable reason would be you didn't get the privilages required on the production DB as you have on the test DB.
IHTH,
The most probable reason would be you didn't get the privilages required on the production DB as you have on the test DB.
IHTH,
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
![Image](http://www.worldcommunitygrid.org/images/logo.gif)
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
![Image](http://www.worldcommunitygrid.org/images/logo.gif)
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Specifically, you lack SELECT privilege on the system tables in which names of tables, views, columns and so on are stored. Negotiate with your DBA, pointing out that SELECT privilege alone can not engender any damage,
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Premium Member
- Posts: 108
- Joined: Sat Feb 05, 2005 6:52 pm
- Location: US
Hmm,
Are both projects same in configuration?
How did you promote the job to production?
make sure the users used have exactly the same profile on both DBs.
did you find anything along those lines?
Are both projects same in configuration?
How did you promote the job to production?
make sure the users used have exactly the same profile on both DBs.
did you find anything along those lines?
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
![Image](http://www.worldcommunitygrid.org/images/logo.gif)
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
![Image](http://www.worldcommunitygrid.org/images/logo.gif)
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
-
- Premium Member
- Posts: 108
- Joined: Sat Feb 05, 2005 6:52 pm
- Location: US
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
Maybe there was more words in the message....something like the one below
Note - all actions are to be checked from the DS server and not from the client.
Find the full error description and give it to your dba as it is the DB2 error that is stopping."Error: [IBM][CLI Driver][DB2]SQL0471N Invocation of routine "SYSIBM. SQLTABLES " failed due to reason "00E7900C". SQLSTATE=55023, Connector 'db2', Method -Catalog[Metadata]- (-471)$$BUILDLIST:210"
Note - all actions are to be checked from the DS server and not from the client.
I'd also recommend trying a manual export import of the job via manager to see if you get a different error code.
I had something similar in EE and a no warning job came up with warning after being promoted via VC.
I exported/imported it and got another warning, So it's worth a check.
IHTH,
I had something similar in EE and a no warning job came up with warning after being promoted via VC.
I exported/imported it and got another warning, So it's worth a check.
IHTH,
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
![Image](http://www.worldcommunitygrid.org/images/logo.gif)
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
![Image](http://www.worldcommunitygrid.org/images/logo.gif)