DB2 - Problembeschreibung
Problem IC85808 | Status: Geschlossen |
SYSINSTALLOJECTS may fail to create SECURED Triggers on POLICY table | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
Starting with DB2 V10.1 triggers on POLICY table are created with option SECURED. This requires the user running procedure SYSINSTALLOBJECTS to have SECADM or CREATE_SECURE_OBJECT authority on the database. Without these authorities granted to the user the procedure SYSINSTALLOBJECTS will not create all the needed triggers on the POLICY table. The procedure call itself will return successfully, hence giving no indication of missing objects. But subsequent actions like the attempt to verify the POLICY table or retrieving a policy will result in error SQL0438N or SQL1439N as shown below: db2 "call sysproc.sysinstallobjects( 'POLICY', 'V', 'SYSTOOLSPACE', 'SYSTOOLS' )" SQL0438N Application raised error or warning with diagnostic text: "POLICY INVALID". SQLSTATE=3900 db2 "call sysproc.automaint_get_policyfile( 'MAINTENANCE_WINDOW', 'maintenance_window.xml' )" SQL1439N Could not retrieve automated maintenance policy configuration information. SQLSTATE=3900 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 2. * **************************************************************** | |
Local-Fix: | |
- grant either SECADM or CREATE_SECURE_OBJECT authority to the user who is creating the POLICY table | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 Version 10.1 Fix Pack 2. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 09.08.2012 07.01.2013 07.01.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.2 | |
10.5.0.2 |