Job Management Partner 1/Automatic Job Management System 3 Command Reference 2
Format
ajsembdbunset {-r[-e]|-e[-r]} [-id embedded-database-setup-identifier] [-i embedded-database-practical-directory-name]Format 1 (for canceling the setup of the embedded database (UNIX only))
ajsembdbunset -r [-id embedded-database-setup-identifier] [-i embedded-database-practical-directory-name]Format 2 (for deleting the embedded database environment)
ajsembdbunset -e [-id embedded-database-setup-identifier] [-i embedded-database-practical-directory-name]
Description
Cancels the setup of the embedded database.
You can execute this command regardless of the operating status of the embedded database. You can execute the command only when all the scheduler services for which the target embedded database has been created as the scheduler database are inactive.
Execution privileges
In Windows: Administrators privileges
In UNIX: Superuser privileges
Storage directory
- In Windows:
- JP1/AJS3 - Manager-installation-folder\tools\
- In UNIX:
- /opt/jp1ajs2/tools/
Arguments
-r
Specify this option to upgrade the embedded database.
This option is for UNIX only.
When you execute the command with this option, the registration of the embedded database running in the specified directory is canceled in the operating system. However, the embedded database environment is not deleted.
-e
Specify this option to delete the embedded database environment.
The data in the embedded database will be deleted. If you want to keep the data, save it somewhere else beforehand.
In UNIX, if the -e option is specified, the -r option is also implicitly specified. That is, the registration of the embedded database running in the specified directory is canceled in the operating system.
-id embedded-database-setup-identifier
Use four characters, _JNn (N: the character specified during setup of the embedded database environment, n: 0 to 9 or A to Z), to specify the setup identifier of the embedded database.
If you omit this option, the system assumes _JF0.
To check the registered setup identifiers and embedded database practical directories, execute the ajsembdbidlist command.
For details on the ajsembdbidlist command, see ajsembdbidlist in 2. Commands Used during Setup.
-i embedded-database-practical-directory-name
Specify the name of the embedded database practical directory.
You must specify this option only when cancellation of the setup specified by using the -id option fails for example, when the ajsembdbbuild command does not end normally.
Notes
- When you execute ajsembdbunset command, the following message appears:
message: ssss Embeddb DELETE?(y/n):
ssss: setup-identifier
This is a confirmation message for asking you whether you want to delete the environment. If the deletion will cause no problems, enter y.
- When you execute ajsembdbunset command, check whether the specified operation directory is correct.
- Before you execute ajsembdbunset command, stop all the JP1/AJS3 services, and the JP1/AJS3 Console Agent service on the JP1/AJS3 - Manager host (including logical hosts). The command may end normally even if you execute the command without stopping the services.
- The ajsembdbunset command forcibly shuts down the embedded database even if the scheduler service is operating. You need to check whether the scheduler service is operating.
- The ajsembdbunset command is implemented by a script. If you specify an illegally long character string or a invalid character string or value for the options, an unexpected error may occur. You must specify a character string or a number within the range specified by the DBMS and JP1/AJS3.
- Do not execute ajsembdbunset command repeatedly in quick succession. If you do so, the following problems might occur:
- The message output is invalid. For example, an invalid message is output or a message that should be output is not output.
- The ajsembdbunset command results in an error.
- When you specify only the -r option to remove registration of the embedded database from the operating system, you cannot execute the commands that operate on the embedded database until the embedded database upgrade has been completed. If you execute such a command, it outputs the following message and results in an error: KAVS2115-E Embedded service is not installed.
- In a cluster system, execute the ajsembdbunset command on both the primary and secondary hosts. On the primary host (the host specified in the -eh option of the ajsembdbbuild command), make sure that the shared disk is mounted before executing the ajsembdbunset command. You must execute the ajsembdbunset command on the primary host first. If you attempt to execute the ajsembdbunset command on the secondary host with the shared disk mounted before executing the command on the primary host, the following message is output and an error occurs: KFPS04619-E Unable to execute aa....aa command due to HiRDB unit not offline or not terminate normally(S+R). If this message is output, execute the ajsembdbunset command on the primary host with the shared disk mounted, and then re-execute the ajsembdbunset command with the -i option specified on the secondary host.
- If the embedded database has been stopped forcibly or has terminated abnormally, restart it, normally terminate it, and then execute the command.
Return values
0 Ends normally Values other than 0 Ends abnormally
Actions to be taken if an error occurs
If an error occurs, take the action indicated in the following table.
Message ID Phenomenon Action taken KAVS0996-E The specified option is incorrect. Check the specification of the option. KAVS2104-E The embedded database is not set up. The environment of the embedded database has already been deleted. KAVS2115-E The embedded database is not installed. The embedded database to be deleted is not installed. KAVS2116-E The specified option is incorrect. Check the option output in the message and re-execute the command. KAVS2117-E An error occurred when you executed the command. Check the message output in the maintenance information.
Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.