CA WAAE new install or upgrade fails during the Event Server (DB) creation when using Oracle Database.
Article ID: 6761
Updated On:
Products
Issue/Introduction
CA Workload Automation AE (WAAE) installation, new or upgrade, fails during the Event Server (AEDB) creation when using Oracle Database server.
The WAAE installation log [CAWorkloadAutomationAE.log in $CASHCOMP/installer/log directory on Unix or Linux | Install(%AUTOSERV%).log or Install_Upgrade.log in the %AUTOROOT% folder on Windows] shows errors similar to the following;
11:29:41 ++ -- WA: CreateAEDB.pl for Oracle failed. For more information, see: /opt/CA/SharedComponents/installer/log/CAWorkloadAutomationAE.log
11:29:41 ++ -- WA: Also, see: /tmp/ora_createaedb_pri
CreateAEDB: CA Workload Automation AE database was not created or updated. Please check /tmp/ora_createaedb_pri/install_aedb.log for details.
And the install_aedb.log file contains errors:
-------------------------------------------------------------------------------
SQL*Plus: Release 11.2.0.3.0 Production on Tue Mar 14 12:29:41 2017
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Error accessing PRODUCT_USER_PROFILE
Warning: Product user profile information not loaded!
You may need to run PUPBLD.SQL as SYSTEM
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining,
Oracle Database Vault and Real Application Testing options
...
...
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining,
Oracle Database Vault and Real Application Testing options
Return code = 256
CA Workload Automation AE database was not created or updated.
-------------------------------------------------------------------------------
Environment
Cause
The WAAE DB creation module (CreateAEDB.pl) failed because of the following Oracle SQL*Plus Warning received when logging on to the Oracle server as the aedbadmin user.
Error accessing PRODUCT_USER_PROFILE
Warning: Product user profile information not loaded!
You may need to run PUPBLD.SQL as SYSTEM
Although these messages are warnings, it may be seen as a symptom of not following our instructions and/or database template during installation.
These associated error messages are warning you that the PRODUCT_USER_PROFILE table has not been built in the SYSTEM schema. If the PRODUCT_USER_PROFILE table is created incorrectly, all users other than SYSTEM will see a warning when connecting to Oracle from SQL*Plus that the product user profile information is not loaded.
Resolution
Executing the PUPBLD.SQL script is required to prevent the SQL*Plus warning messages that are associated to user profile information.
To create the PRODUCT_USER_PROFILE table, a Database Administrator (DBA) must run the PUPBLD.SQL script located in the Oracle home directory. This script must be run as user SYSTEM.
After the PUPBLD.SQL script has been successfully executed by the Oracle DBA as the SYSTEM user, rerun the CA WAAE installation.
Additional Information
Feedback
