Highlighted
Absent Member.. sroutz Absent Member..
Absent Member..
1559 views

OML on RHEL 6.4 - Startup data already in table opc_mgmtsv_config

Jump to solution

Hello,

I am installing OML 9.10 on RHEL 6.4 (with external Oracle DB).

After the installation of HPOM, the configuration step failed and I realized that the latest patch is required.

I installed latest patch OML_00071, then I run 'opcdbinit -c' (this is supposed to "clear" all tables?) and re-started the configuration procedure.

Now, I get the following error message:

 

         Uploading functions and triggers into the database ...
         Loading the initial configuration into the database ...
    Warning opc_dbinit(5088) : Startup data already in table opc_mgmtsv_config. (OpC55-33)
    ERROR:   opcdbinit aborted because startup data is present.
    ERROR:   Error occurred in the program opcdbinit.
         The default configuration is not or not completely loaded.
         Run 'opcdbinit -c' to re-initialize the database after you fixed the problems.
         opcdbsetup had Errors.

Should I manually clear this table, and repeat the configuration procedure?

Thanks,

 

 

0 Likes
1 Solution

Accepted Solutions
Micro Focus Expert
Micro Focus Expert

Re: OML on RHEL 6.4 - Startup data already in table opc_mgmtsv_config

Jump to solution

Hello,

 

If "opcdbsetup -p" succeeded (it looks like it did as the error message was "just" a warning), then you're OK. The DB was configured OK.

 

For a remote DB installation, opcdbsetup will not create opc_report (it is a documented step in the installation guide that you or your DBA do when you pre-create the remote DB).

 

Best regards,

Tobias

 

View solution in original post

5 Replies
sekar sundaram Absent Member.
Absent Member.

Re: OML on RHEL 6.4 - Startup data already in table opc_mgmtsv_config

Jump to solution

I am not sure of this issue.. but when i read the manuals, may be you can run opcdbinit with a "-v" (verbose mode) which may give some more info..

 

Just to reiterate the steps:

 

Reinitializing the HPOM Database and Configuration
If required, you can reinitialize the HPOM database and configuration
on the management server after reinstalling the HPOM software.
To reinitialize the database and configuration, follow these steps:
1. If required, deinstall the HPOM software from all the managed
nodes as described in the HPOM Administrator’s Reference.
CAUTION After you reinitialize the HPOM database, all the node configuration
is lost. You must reconfigure the nodes.
2. As user root, export the Oracle variables as follows:
export ORACLE_HOME=/opt/oracle/product/<version>
export ORACLE_BASE=/opt/oracle
3. If the software was deinstalled, reinstall it as described in
“Reinstalling the HPOM Software” on page 174.
4. Stop the HP Operations server and agent processes:
/opt/OV/bin/OpC/opcsv -stop
/opt/OV/bin/ovc -stop AGENT
5. Clean the database, including the configuration for operators and
nodes, and all active and history messages.
Enter:
su - root
/opt/OV/bin/OpC/opcdbinit -c [-v]
exit
The opcdbinit command uses the following modes:
-c Clean mode. Cleans up tables and loads the default
configuration.
-v Verbose mode. Used to show the detailed
processing progress.

6. Restart all the HP Operations management server and agent

processes by entering:
/opt/OV/bin/OpC/opcsv -start
/opt/OV/bin/ovc -start AGENT

 

 

One more tip:

The database configuration step can be done manually by using

opcdbsetup -p.

Absent Member.. sroutz Absent Member..
Absent Member..

Re: OML on RHEL 6.4 - Startup data already in table opc_mgmtsv_config

Jump to solution
thank you, sekar.

/opt/OV/bin/OpC/opcdbinit -v
returns the same warning!
Warning opc_dbinit(11621) : Startup data already in table opc_mgmtsv_config. (OpC55-33)
QUERY: You can abort the initialization or reload the initial data. If you continue, all running HPOM processes will be stopped. Do you want to clear and re-initialize the database (y/n) [y] ?

Answering [y] didn't help, again the configuration fails.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: OML on RHEL 6.4 - Startup data already in table opc_mgmtsv_config

Jump to solution

Hello,

 

Please call opcdbinit with both, -c and -v:

# opcdbinit -c -v

 

If that also fails, please provide the output.

 

Best regards,

Tobias

 

0 Likes
Absent Member.. sroutz Absent Member..
Absent Member..

Re: OML on RHEL 6.4 - Startup data already in table opc_mgmtsv_config

Jump to solution

Hello Tobias.

 

# opcdbinit -c -v

is successful

 

Then, when

# ovoconfigure

asks whether you want to set up the database manually, I pause and, from a different shell, I run

# opcdbsetup -p

which is successful, but with the same WARNING msg

Warning opc_dbinit(5088) : Startup data already in table opc_mgmtsv_config. (OpC55-33)

 

Then, I continue with # ovoconfigure, but it fails with the same ERROR

    Warning opc_dbinit(5088) : Startup data already in table opc_mgmtsv_config. (OpC55-33)
    ERROR:   opcdbinit aborted because startup data is present.

 

 

******** a WorkAround(?)

I rerun # ovoconfigure and, when asked for DB configuration, I answered [no]

     ------------------------
      Database configuration
     ------------------------
     - Configure the database [exit,back,?,y|n,"y"] ?
     > n
and at that point, I manually performed this step, with # opcdbsetup,

but I skipped the Configuration Checks in # ovoconfigure

 

The HPOM configuration continued with  "Server initialization" and   "Server final configuration" etc

Still, I am not sure that the DB configuration was complete.

For example, ( # opcdbsetup -p ) didn't ask for the opc_report password, but ( # ovoconfigure ) does.

 

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: OML on RHEL 6.4 - Startup data already in table opc_mgmtsv_config

Jump to solution

Hello,

 

If "opcdbsetup -p" succeeded (it looks like it did as the error message was "just" a warning), then you're OK. The DB was configured OK.

 

For a remote DB installation, opcdbsetup will not create opc_report (it is a documented step in the installation guide that you or your DBA do when you pre-create the remote DB).

 

Best regards,

Tobias

 

View solution in original post

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.