Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / Informix Topics / October 2003

Tip: Looking for answers? Try searching our database.

ISM Startup Errors

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
sree_oradba - 29 Oct 2003 01:10 GMT
Hi,

I am Oracle DBA new to Informix.  IDS version 9.3 on AIX: 4.3

I was trying to configure ISM.  I got it up and running as per the
manual last week.  Today when I typed "ism_watch" I got an error saying
server not available. I couldn't find any nsr deamons.  I wanted to re-
start the ISM.  When I try to start the ISM (as root) I get the
following output:

----------------------------------

start_ism: is starting the ISM daemons.

*** The environment variable PRINTER is not set.

   The ISM server cannot print important bootstrap information.

   To perform a full ISM recovery, e.g. from a disk failure, use

   'ism_catalog -find_bootstrap'.

ism_startup: Initializing the ISM server.

create failed: A group already exists named 'ISMDiskData'

create failed: save set of /dev/null would be specified by two

create failed: There is already a `NSR label' with name `ISMDiskData'

create failed: There is already a `NSR pool' with name `ISMDiskData'

create failed: A group already exists named 'ISMDiskLogs'

create failed: save set of /dev/null would be specified by two

create failed: There is already a `NSR label' with name `ISMDiskLogs'

create failed: There is already a `NSR pool' with name `ISMDiskLogs'

create failed: A group already exists named 'ISMData'

create failed: save set of /dev/null would be specified by two

create failed: There is already a `NSR label' with name `ISMData'

create failed: There is already a `NSR pool' with name `ISMData'

create failed: A group already exists named 'ISMLogs'

create failed: save set of /dev/null would be specified by two

create failed: There is already a `NSR label' with name `ISMLogs'

create failed: There is already a `NSR pool' with name `ISMLogs Clone'

create failed: A policy already exists with name '6 Months'

----------------------------------------------------

Can I ignore these Messages?

Also, When I try to  run the following steps,

-----------------

ism_add -device $SM_DISKDEV1 -type file

ism_add -device $SM_DISKDEV2 -type file

ism_op -label $SM_DISKDEV1 -pool ISMDiskData -volume ISMData

ism_op -label $SM_DISKDEV1 -pool ISMDiskLogs -volume ISMLogs

ism_op -mount $SM_DISKDEV1

ism_op -mount $SM_DISKDEV2

-------------------------------

I get a message saying that

----------------------

Tue 17:56:52 /fs/backup/dbqa/dbspaces duplicate name; pick new
name or delete

---------------

I unmounted the device and I still get the error.

Can someone tell what I am doing wrong or everything is fine???

Thanks,

Sree
The Big Potatoe - 29 Oct 2003 12:24 GMT
> Hi,
>
[quoted text clipped - 95 lines]
> --
> Posted via http://dbforums.com

Sounds like you are doing an ism_startup -init.

You only need to do the -init to do the first initialisation, afterwards
use ism_startup.

The ism daemon is coming along and trying to add NSRLabel and NSRPools
which already exist.

Use ism_show -volumes and ism__show -volume "volume_name" to confirm
what you have actually got in ISM.
Bickel - 29 Oct 2003 13:32 GMT
> I was trying to configure ISM.  I got it up and running as per the
> manual last week.  Today when I typed "ism_watch" I got an error saying
[quoted text clipped - 4 lines]
> start_ism: is starting the ISM daemons.
> *** The environment variable PRINTER is not set.

> ism_startup: Initializing the ISM server.
> create failed: A group already exists named 'ISMDiskData'
DELETED
> Can I ignore these Messages?

The first error about the printer var is one you can ignore if you
don't want a printout of the bootstrap (if you have this printout it
could save you much time when you are restoring)

The other errors indicate that you start ism with the -init flag, this
flag is only needed the first time that you start ism, or when you
want to re-initialize it.
So just start it without flags.

> Also, When I try to  run the following steps,
> ism_add -device $SM_DISKDEV1 -type file
[quoted text clipped - 3 lines]
> ism_op -mount $SM_DISKDEV1
> I get a message saying that

>  Tue 17:56:52 /fs/backup/dbqa/dbspaces duplicate name; pick new
>  name or delete
>
> ---------------
>
> I unmounted the device and I still get the error.

Here you try to add a device wich is already there, nothing to do with
mounting.
Please read backup guide....
Ronald
sree_oradba - 29 Oct 2003 17:26 GMT
Hey,

Thanks for your input.  I started ISM without -init. It seemed fine.

When I try to take a backup, nothing happens.  This ithe ISA output

------------------------------------------------------------------

55638 2003-10-29 10:01:09 Successfully connected to Storage Manager.

 55638 2003-10-29 10:01:08 Begin level 0 backup rootdbs.

 55638 2003-10-29 10:01:05 BAR_XFER_BUF_SIZE exceeded maximum allowed
 limit. Changing buffer size to 61440.

 55638 2003-10-29 10:01:05 Logical Logs will not be backed up because
 LTAPEDEV value is /dev/null

----------------------------------------

and it sits there.  When I did the ism_watch on the server, I see
the following

-------------------

Server: speedy           Wed Oct 29 10:06:21 2003

Up Version: Informix_Storage_Manager ISM.2.20.UC1.114-06/06
Server Edition

Saves: 0 session(s)  Recovers: 0 session(s)

Device            type     volume

/dev/rmt0.1      8mm      (none)

/dbqa/dbspaces    file     (none)

/dbqa/logfiles    file     (none)

Messages:

Wed 09:45:44 server notice: started

Wed 09:45:59 index notice: completed checking 2 client(s)

Wed 10:01:09 media info: suggest mounting FAST2.Daily.1.Tuesday.2 on
speedy for writing  to pool 'Default'

Wed 10:01:09 media waiting event: backup to pool 'Default' waiting for
1 writable backup tape(s) or disk(s)

Pending:

Wed 10:01:09 media waiting: backup to pool 'Default' waiting for 1
writable backup tape(s) or disk(s)

----------------------------------------------

Any suggestions on what I am doing wrong? In Messages section, under
devices, I don't see /fs/backup/dbqa/dbspaces. I see only
/dbqa/dbspaces.  Is it a problem?

Here is the output from ism_watch

--------------------

speedy:/usr/local/informix>ism_show -devices

(nothing) mounted on 8mm tape /dev/rmt0.1

(nothing) mounted on file disk /fs/backup/dbqa/dbspaces

(nothing) mounted on file disk /fs/backup/dbqa/logfiles

----------------------------
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.