nv-l
[Top] [All Lists]

RE: Copying Database from 601 to 602

To: nv-l@lists.tivoli.com
Subject: RE: Copying Database from 601 to 602
From: "James Shanks" <SHANKS@us.tivoli.com>
Date: Thu, 18 Oct 2001 11:55:14 -0400
This is a multipart message in MIME format.
Jim -

I was asking about the mapadmin command, not about reset_ci.  The error is 
about the map.
As Steve Hochstedtler indicated, the relevant question is about the maps 
themselves.
What do you get when you issue  mapadmin -l?
What do you get when you try  mapadmin -u <hostname>  or mapadmin -u 
default:,hostname   ?


James Shanks
Level 3 Support 
Tivoli NetView for UNIX and NT
Tivoli Software
IBM Software Group
Please note that my new id is jshanks@us.ibm.com






"Bingen, Jim D" <Jim.Bingen@nav-international.com>
Sent by: owner-nv-l@tkg.com
10/18/2001 10:22 AM
Please respond to IBM NetView Discussion

 
        To:     "'IBM NetView Discussion'" <nv-l@tkg.com>
        cc: 
        Subject:        RE: [NV-L] Copying Database from 601 to 602

 




 

Netview 601 system -

ovstop

tar -cvf nvdb.bak01.tar /usr/OV/databases/openview

ovstart

 

 

Netview 602 system -

ovstop

pax -rp e -f nvdb.bak01.tar

/#/usr/OV/service/reset_ci

 

 Start of reset_ci, after successful completion

 you will receive a reset_ci finished message.

 

 

Reregistering /usr/OV/lrf/ovesmd.lrf...

ovaddobj - Static Registration Utility

WARNING: LRF record #3 conflicts with existing entry--not added. (OVs 
1-17)

WARNING: LRF record #4 conflicts with existing entry--not added. (OVs 
1-17)

Successful Completion

 

Reregistering /usr/OV/lrf/ovelmd.lrf...

ovaddobj - Static Registration Utility

Successful Completion

 

tmf_client_init: o_errs:0014 destination dispatcher unavailable

Unable to update the label for the NetView server icon.

 

reset_ci finished

 

/#

/#ovstart

/#ovstatus

 object manager name: OVsPMD

 behavior:            OVs_PMD

 state:               RUNNING

 PID:                 14728

 exit status:         -

 

 object manager name: ovwdb

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 16008

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: nvsecd

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 14966

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: pmd

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 4762

 last message:        pmd completed initialization

 exit status:         -

 

 object manager name: OVORS_M

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 18062

 last message:        orsd completed initialization

 exit status:         -

 

 object manager name: trapd

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 18320

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: ovtopmd

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 17548

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: trapgend

 behavior:            OVs_NON_WELL_BEHAVED

 state:               RUNNING

 PID:                 16350

 exit status:         -

 

 object manager name: mgragentd

 behavior:            OVs_NON_WELL_BEHAVED

 state:               RUNNING

 PID:                 17082

 exit status:         -

 

 object manager name: ovactiond

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 18580

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: nvcorrd

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 18836

 last message:        Initialization complete

 exit status:         -

 

 object manager name: nvpagerd

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 14494

 last message:        PMD initialization complete

 exit status:         -

 

 object manager name: actionsvr

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 20386

 last message:        Initialization complete

 exit status:         -

 

 object manager name: nvserverd

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 19358

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: nvcold

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 16772

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: snmpCollect

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 19098

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: nvlockd

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 17290

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: netmon

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 20218

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: C5d

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 29930

 last message:        Initialization complete

 exit status:         -

 

 object manager name: ems_sieve_agent

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 29412

 last message:        

 exit status:         -

 

 object manager name: ems_log_agent

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 29670

 last message:        

 exit status:         -

 

/#nv6000

portmap is already running 

Starting Tivoli NetView daemons : 

Daemon startup completed

Starting user interface applications...

Wed Oct 17 15:54:27 CDT 2001

Please see //nv6000.log if you have startup errors.

/#

 

At this point the Tivoli NetView screen comes up, it says Initializing... 
accross the bottom, and when Opening Map comes up, I get a pop up window 
that says "Could not open map: default.  Map exists on machine:  5xx"

 

When I click the OK button, both screens exit. I will include the 
nv6000.log.

 

 

 

Jim Bingen

International Truck and Engine Corp.

Staff Specialist, Network Support Services

P(262)780-5345

F(262)780-5376

mailto:jim.bingen@nav-international.com

   

 

-----Original Message-----
From: James Shanks [mailto:SHANKS@us.tivoli.com]
Sent: Wednesday, October 17, 2001 2:05 PM
To: IBM NetView Discussion
Subject: RE: [NV-L] Copying Database from 601 to 602

 


Then you may have to talk to support some more because mapadmin -u, if 
entered correctly, should have fixed it.
There is no theoretical reason why data cannot be transported between 
6.0.1 and 6.0.2, unless the original tar was bad.  And reset_ci also does 
the mapadmin command under the covers so there is usually no reason to do 
it afterward.

What exactly did you enter and what exactly did you get back?

James Shanks
Level 3 Support  
Tivoli NetView for UNIX and NT
Tivoli Software
IBM Software Group
Please note that my new id is jshanks@us.ibm.com






 


"Bingen, Jim D" <Jim.Bingen@nav-international.com>
Sent by: owner-nv-l@tkg.com

10/17/2001 02:40 PM
Please respond to IBM NetView Discussion


        
        To:        "'IBM NetView Discussion'" <nv-l@tkg.com>
        cc:        
        Subject:        RE: [NV-L] Copying Database from 601 to 602

       




I tried the mapadmin ?u command but it didn't help. I still received the 
same error message.

 

 

-----Original Message-----
From: CATALINA MARTINEZ [mailto:CATALINA.MARTINEZ@tlc.state.tx.us]
Sent: Wednesday, October 17, 2001 12:42 PM
To: nv-l@tkg.com
Subject: Re: [NV-L] Copying Database from 601 to 602

  

Jim,

 

you may try:

 

mapadmin -u mapname:hostname.

 

I moved my db from 6.0 to 6.02  and did not have this particular problem. 
But I came across this command when I was searching this list on the 
procedures to do it.

 

I dont know if it still works.

 

Catalina



>>> Jim.Bingen@NAV-INTERNATIONAL.com 10/17/01 11:46AM >>>
I am moving from Netview version 6.0.1 on AIX 4.3.3, to Netview 6.0.2 also
on AIX 4.3.3. I tried copying the database files using the tar/pax method
recommended by Leslie, did a reset_ci, did the ovw 
-fields/-verify/-config,
but I am getting the error "Could not open map: default. Map exists on
machine 5xx". I called support (PMR 78535,379) but they did not think I
could copy the database between versions 601 and 602.

Has anybody tried this? Any luck?

Thanks.


_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l 


#### nv6000.log has been removed from this note on October 18 2001 by 
James Shanks


Jim -

I was asking about the mapadmin command, not about reset_ci.  The error is about the map.
As Steve Hochstedtler indicated, the relevant question is about the maps themselves.
What do you get when you issue  mapadmin -l?
What do you get when you try  mapadmin -u <hostname>  or mapadmin -u default:,hostname   ?


James Shanks
Level 3 Support  
Tivoli NetView for UNIX and NT
Tivoli Software
IBM Software Group
Please note that my new id is jshanks@us.ibm.com




"Bingen, Jim D" <Jim.Bingen@nav-international.com>
Sent by: owner-nv-l@tkg.com

10/18/2001 10:22 AM
Please respond to IBM NetView Discussion

       
        To:        "'IBM NetView Discussion'" <nv-l@tkg.com>
        cc:        
        Subject:        RE: [NV-L] Copying Database from 601 to 602

       





 

Netview 601 system -

ovstop

tar -cvf nvdb.bak01.tar /usr/OV/databases/openview

ovstart

 

 

Netview 602 system -

ovstop

pax -rp e -f nvdb.bak01.tar

/#/usr/OV/service/reset_ci

 

 Start of reset_ci, after successful completion

 you will receive a reset_ci finished message.

 

 

Reregistering /usr/OV/lrf/ovesmd.lrf...

ovaddobj - Static Registration Utility

WARNING: LRF record #3 conflicts with existing entry--not added. (OVs 1-17)

WARNING: LRF record #4 conflicts with existing entry--not added. (OVs 1-17)

Successful Completion

 

Reregistering /usr/OV/lrf/ovelmd.lrf...

ovaddobj - Static Registration Utility

Successful Completion

 

tmf_client_init: o_errs:0014 destination dispatcher unavailable

Unable to update the label for the NetView server icon.

 

reset_ci finished

 

/#

/#ovstart

/#ovstatus

 object manager name: OVsPMD

 behavior:            OVs_PMD

 state:               RUNNING

 PID:                 14728

 exit status:         -

 

 object manager name: ovwdb

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 16008

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: nvsecd

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 14966

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: pmd

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 4762

 last message:        pmd completed initialization

 exit status:         -

 

 object manager name: OVORS_M

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 18062

 last message:        orsd completed initialization

 exit status:         -

 

 object manager name: trapd

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 18320

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: ovtopmd

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 17548

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: trapgend

 behavior:            OVs_NON_WELL_BEHAVED

 state:               RUNNING

 PID:                 16350

 exit status:         -

 

 object manager name: mgragentd

 behavior:            OVs_NON_WELL_BEHAVED

 state:               RUNNING

 PID:                 17082

 exit status:         -

 

 object manager name: ovactiond

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 18580

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: nvcorrd

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 18836

 last message:        Initialization complete

 exit status:         -

 

 object manager name: nvpagerd

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 14494

 last message:        PMD initialization complete

 exit status:         -

 

 object manager name: actionsvr

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 20386

 last message:        Initialization complete

 exit status:         -

 

 object manager name: nvserverd

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 19358

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: nvcold

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 16772

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: snmpCollect

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 19098

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: nvlockd

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 17290

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: netmon

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 20218

 last message:        Initialization complete.

 exit status:         -

 

 object manager name: C5d

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 29930

 last message:        Initialization complete

 exit status:         -

 

 object manager name: ems_sieve_agent

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 29412

 last message:       

 exit status:         -

 

 object manager name: ems_log_agent

 behavior:            OVs_WELL_BEHAVED

 state:               RUNNING

 PID:                 29670

 last message:       

 exit status:         -

 

/#nv6000

portmap is already running

Starting Tivoli NetView daemons :

Daemon startup completed

Starting user interface applications...

Wed Oct 17 15:54:27 CDT 2001

Please see //nv6000.log if you have startup errors.

/#

 

At this point the Tivoli NetView screen comes up, it says Initializing... accross the bottom, and when Opening Map comes up, I get a pop up window that says "Could not open map: default.  Map exists on machine:  5xx"

 

When I click the OK button, both screens exit. I will include the nv6000.log.

 

 

 

Jim Bingen

International Truck and Engine Corp.

Staff Specialist, Network Support Services

P(262)780-5345

F(262)780-5376

mailto:jim.bingen@nav-international.com

  

 

-----Original Message-----
From: James Shanks [mailto:SHANKS@us.tivoli.com]
Sent: Wednesday, October 17, 2001 2:05 PM
To: IBM NetView Discussion
Subject: RE: [NV-L] Copying Database from 601 to 602

 


Then you may have to talk to support some more because mapadmin -u, if entered correctly, should have fixed it.
There is no theoretical reason why data cannot be transported between 6.0.1 and 6.0.2, unless the original tar was bad.  And reset_ci also does the mapadmin command under the covers so there is usually no reason to do it afterward.

What exactly did you enter and what exactly did you get back?

James Shanks
Level 3 Support  
Tivoli NetView for UNIX and NT
Tivoli Software
IBM Software Group
Please note that my new id is jshanks@us.ibm.com





 

"Bingen, Jim D" <Jim.Bingen@nav-international.com>
Sent by: owner-nv-l@tkg.com

10/17/2001 02:40 PM
Please respond to IBM NetView Discussion

       
        To:        "'IBM NetView Discussion'" <nv-l@tkg.com>
        cc:        
        Subject:        RE: [NV-L] Copying Database from 601 to 602

       




I tried the mapadmin –u command but it didn't help. I still received the same error message.

 

 

-----Original Message-----
From: CATALINA MARTINEZ [mailto:CATALINA.MARTINEZ@tlc.state.tx.us]
Sent: Wednesday, October 17, 2001 12:42 PM
To: nv-l@tkg.com
Subject: Re: [NV-L] Copying Database from 601 to 602

 

Jim,

 

you may try:

 

mapadmin -u mapname:hostname.

 

I moved my db from 6.0 to 6.02  and did not have this particular problem. But I came across this command when I was searching this list on the procedures to do it.

 

I dont know if it still works.

 

Catalina



>>> Jim.Bingen@NAV-INTERNATIONAL.com 10/17/01 11:46AM >>>
I am moving from Netview version 6.0.1 on AIX 4.3.3, to Netview 6.0.2 also
on AIX 4.3.3. I tried copying the database files using the tar/pax method
recommended by Leslie, did a reset_ci, did the ovw -fields/-verify/-config,
but I am getting the error "Could not open map: default. Map exists on
machine 5xx". I called support (PMR 78535,379) but they did not think I
could copy the database between versions 601 and 602.

Has anybody tried this? Any luck?

Thanks.


_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l


#### nv6000.log has been removed from this note on October 18 2001 by James Shanks




<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web