Load application database attributes and values
Function: The Load Application Database Attributes utility provides an efficient method of assigning attributes to a large number of application databases.
Take the following steps to load application database attributes and values:
Create a CSV File of Application Database Objects and Attributes.
Execute the Load Application Database Attribute Utility.
Verify the Application Database Attributes Load.
Create a report template using the SQL Template Designer.
Once attribute values are assigned to application databases, a SQL Template Designer report can query the database to report on the application databases.
The LoadDBAttribute utility assigns application attribute values to a host's database application. This utility takes as input a comma-separated values (CSV) file.
Note:
This CSV file becomes the primary document of record for Application Database Attributes and therefore should be preserved in a working directory for future updates.
Create a spreadsheet table, in the format shown in the following example, and save it as a CSV file in a working directory. This file is specific to application databases.
In the above example:
The first 3 columns comprise the unique identifier for an Application Database--in this example, CorpServer1, FinanceDB, and FinanceDBInstance.
Subsequent columns list the attributes and values.
Columns list the objects that uniquely identify an application. For an Application Database, the required columns are: Host Name, DB Name, DB Instance.
Each additional column lists attributes and values.
First (Header) Row - Contains the fields that uniquely identify an application, followed by the attribute names. The header row is information only and is not processed as a data row.
Subsequent rows list the objects that uniquely identify an application database, followed by the attribute values that you are assigning to each application database.
Bulk Load utilities must be run in SQLPLUS as user APTARE. The load_package utility is located in:
/opt/aptare/database/stored_procedures (Linux) \opt\oracle\database\stored_procedures (Windows)
To assign attributes to application databases
- Create a table in a spreadsheet.
- Save the table as a comma-separated file (for example, DBAttributes.csv).
- Log in to the Portal server.
- At the command line:
su - aptare
- At the command line, launch sqlplus:
sqlplus <pwd>/<pwd>@//localhost:1521/scdb
Example: sqlplus portal/portal@//localhost:1521/scdb
Execute the following at the SQL prompt:
SQL> Execute load_package.loadDBAttributeFile ('pathname_and_filename','domain_name', db_name_column_num,db_instance_column_num,host_name_column_num, 'log_path_name','log_file_name','check_valid_value');
Where:
'pathname_and_filename'
Full path + filename (enclosed in single straight quotes) of the CSV file
Windows Example: 'c:\config\DBAttributes.csv'
Linux Example: '/config/DBAttributes.csv'
'domain_name'
Name (enclosed in single straight quotes) of the domain in which the host groups and hosts reside; Example: 'DomainEMEA'
db_name_column_num
Column number in the csv file where the DB Name is listed; Example: 2
db_instance_column_num
Column number in the csv file where the DB Instance is listed; Example: 3
host_name_column_num
Column number in the csv file where the Host Name is listed; Example: 1
'log_path_name'
Full path (enclosed in single straight quotes) where the log file will be created/updated; verify that you have write access to this directory.
Optional: If a log path and filename are not specified, log records are written to scon.log and scon.err. To omit this parameter, enter: ''
Example: 'c:\configs'
'log_file_name'
Log file name enclosed in single straight quotes.
Optional: If a log path and filename are not specified, entries are written to scon.log and scon.err. To omit this parameter, enter: ''
Example: 'DBAttributes.log'
'check_valid_value'
'Y' or 'N' enclosed in single straight quotes.
Y - Checks if the attribute value exists. If the utility determines that the attribute value is not valid, it skips this row and does not assign the attribute value to the application database.
N - Updates without checking that the attribute value exists. This option is seldom chosen, but it is available for certain customer environments where attributes may have been created without values (with scripts that bypass the user interface).
Example:
SQL> Execute load_package.loadDBAttributeFile('/config/DBAttributes.csv', 'DomainEMEA', 2, 3, 1,'/config/logs','DBAttributes.log','Y'); - Check the log file for status and errors.
- Restart the Portal services so that the newly added attributes become available in the Dynamic Template Designer.
To verify that the attribute load took effect:
In the Portal, go to .
Select a blue user folder.
Select .
With the SQL Template Designer open, click the tab.
Enter the following query in the SQL Template Designer to verify Application Database attributes:
select * from aps_v_database_attribute