Ibm Sql Error 551
Contents |
DB2 SQL Error:
Sql0551n Sqlstate=42501
SQLCODE=-551, SQLSTATE=42501 db2; SQLCODE=-551; SQLSTATE=42501; permissions Technote (troubleshooting) db2 sql error: sqlcode=-727, sqlstate=56098 Problem After a successful database-transfer to DB2 the Portal Server will not start
Db2 Sql Error Sqlcode=-551 Sqlstate=42501 Sqlerrmc= Select
correctly and the Portal startup shows the following error in the SystemOut.log... com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-551, SQLSTATE=42501, SQLERRMC=DB2USER;EXECUTE;SYSIBM.SQLTABLES, DRIVER=4.18.60 http://www.ibm.com/support/knowledgecenter/SSEPEK_10.0.0/codes/src/tpc/n551.html Symptom The Portal Server is not accessible via a browser after startup. Review of the SystemOut.log shows the following... com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-551, SQLSTATE=42501, SQLERRMC=DB2USER;EXECUTE;SYSIBM.SQLTABLES, DRIVER=4.18.60 Cause The DB2 environment does not have the permissions required for Portal operation Environment http://www-01.ibm.com/support/docview.wss?uid=swg21688020 Portal 8.5 DB2 AIX Diagnosing the problem Review the SystemOut.log and it shows the following during Portal startup... com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-551, SQLSTATE=42501, SQLERRMC=DB2USER;EXECUTE;SYSIBM.SQLTABLES, DRIVER=4.18.60 Research of the DB2 error codes SQLCODE=-551, SQLSTATE=42501 point to a permission's issue...see link for details... http://www.sqlerror.de/db2_sql_error_-551_sqlstate_42501.html Interpreting the SQLERRMC message is very helpful. In this case it is... SQLERRMC=DB2USER;EXECUTE;SYSIBM.SQLTABLES This simply means that the user 'DB2USER' is attempting to perform an EXECUTE statement against the database object 'SYSIBM.SQLTABLES' and cannot due to lack of permissions. Resolving the problem Have the DBA correct the issue and provide the permissions needed. The following Portal links can help provide guidance on the proper permissions that Portal expects... http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/eua-workflows/kc-db-setupdb-db2.dita?lang=en http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/eua-workflows/kc-db-grantpermrun-db2.dita?lang=en Document information More support for: WebSphere Portal Database Connectiv
A fix is available Obtain the fix http://www.ibm.com/support/docview.wss?uid=isg1PM90156 for this APAR. Subscribe You can track all active APARs http://www.dbforums.com/showthread.php?1641803-ERROR-SQLCODE-quot-551-quot-SQLSTATE-quot-42501-quot-when-doing-inserts for this component. APAR status Closed as program error. Error description Optim/z ACCESS gets SQL error -551 when browsing an SQL view. Extracting DB2 tables including the DB2 objects may fail with -551 on SYSIBM.SYSVIEWS, SYSIBM.SYSROUTINES or SYSIBM.TRIGGERS. sql error Local fix 'GRANT' access to SYSIBM.SYSVIEWS. Problem summary **************************************************************** * USERS AFFECTED: * * Optim/z DB2 V10 users without access to 'SYSIBM.SYSVIEWS', * * 'SYSIBM.SYSROUTINES' or 'SYSIBM.TRIGGERS' tables * **************************************************************** * PROBLEM DESCRIPTION: * * Optim/z 'ACCESS' gets SQL error -551 when browsing an SQL * * view. Extracting db2 sql error DB2 tables including the DB2 objects may * * fail with -551 on 'SYSIBM.SYSVIEWS', 'SYSIBM.SYSROUTINES' or * * 'SYSIBM.TRIGGERS'. * **************************************************************** * RECOMMENDATION: * * Apply the provided fix. * **************************************************************** Optim/z uses dynamic SQL for some functions when processing on a DB2 V10 New Function Mode subsystem. If the user is not authorized to access the 'SYSIBM.SYSVIEWS', 'SYSIBM.SYSROUTINES' or 'SYSIBM.TRIGGERS' the request will fail. Problem conclusion The dynamic SQL has been converted to static SQL. This fix changes the product DBRM. A 'REBIND' of Optim DB2 V9 and V10 packages is required after application of the PTF. For releases prior to V10 one only needs to rebind the plans, V10 requires the packages to be rebuilt and rebound because a new V10 specific DBRM has been added. Temporary fix Comments APAR Information APAR numberPM90156 Reported component nameOPTIM MOVE FOR Reported component ID5655V0700
is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 6 of 6 Thread: ERROR SQLCODE "-551", SQLSTATE "42501" when doing inserts. Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 04-28-09,16:14 #1 db2pro View Profile View Forum Posts Banned Join Date Mar 2009 Posts 36 Unanswered: ERROR SQLCODE "-551", SQLSTATE "42501" when doing inserts. Hi All, When I am running the following insert command. I am getting the following error. COMMAND: INSERT INTO WCCADM12.CDEVENTDEFTP ( LANG_TP_CD , EVENTDEF_TP_CD , EVENT_CAT_CD , EVENT_NAME , ENABLE_NOTIFY , EXPIRY_DT , DESCRIPTION , LAST_UPDATE_USER , LAST_UPDATE_DT ) VALUES ( 100, 15, 6, 'PartyComplianceNextVerify', 'Y', null, 'Party Compliance Next Verify Date', null, CURRENT_TIMESTAMP ) ERROR:: DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL0727N An error occurred during implicit system action type "7". Information returned for the error includes SQLCODE "-551", SQLSTATE "42501" and message tokens "WCCADM12|ALTER TABLE|WCCADM12.CDEVENTDEFTP". LINE NUMBER=0. SQLSTATE=56098 When I tried for solutions on google. Many replied that the solution is to 1. drop the triggers related to this table 2. then run the insert commands 3. create the triggers again. The above steps are absolutely working. But as this is in DEV. I am ok to do this and get rid of the issues. But I am worried about doing this in PROD. I just want to know that does anyone has encountered the same issue and could be fixed without dropping and recreating the Triggers. Actually my triggers on this table are for only Updates and Deletes but not on the INSERTS. I am not able to understand why the inserrts are failing. Anyone please help me in finding a solution for this issue wit