SAPDBA brings the following message when starting ("sapdba ... " ):
SAPDBA is already running on this computer with the same operating system user ID (this usually implies with the same database). This is not recommended because the two processes might use resources concurrently. SAPDBA does not check this.
If you choose to continue you will be responsible for all consequences.
Do you want to continue? (y/n) [n] ==>
As SAPDBA can interrupt itself if it called several times simultaneously, SAPDBA initially checks the process list to see if it is already running, that is, id the string "sapdba" is contained in the name. If this is the case, it outputs a corresponding warning message.
The warning also appears if SAPDBA is called from a script, whose name contains this string, although SAPDBA itself is only running once.
The user should decide what to do, depending on the actions planned:
If he is sure that SAPDBA processes will not interfere with each other (for example, if he only wants to start the check functions in the second SAPDBA in the reorganization menu), he can then continue to work with the second SAPDBA (response "... continue ==> y").
However, it is obviously not possible to reorganize the same objects in parallel, or to shut down the database during a reorganization run, and so on. If such actions are planned, you should cancel the second SAPDBA and await termination of the current action in the first SAPDBA (response "... continue ==> n").
Shell scripts that started SAPDBA should not contain the string "sapdba" in their name, to avoid an unnecessary warning message.
You should never rename sapdba so that the string "sapdba" no longer appears in the program name, as the described protective mechanism would then no longer be effective.
Additional key words
sapdba, process list
No comments:
Post a Comment