|
Problem IC85808
|
Status: Closed |
SYSINSTALLOJECTS may fail to create SECURED Triggers on POLICY table |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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 |
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 10.1 Fix Pack 2. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.08.2012
07.01.2013
07.01.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
