Re: ER question
- From: bozon <curtis@xxxxxxxxxxxx>
- Date: Thu, 19 Feb 2009 05:52:55 -0800 (PST)
On Feb 18, 4:19 pm, Madison Pruet <mpru...@xxxxxxxxxxx> wrote:
bozon wrote:
On Feb 18, 2:37 pm, Madison Pruet <mpru...@xxxxxxxxxxx> wrote:
bozon wrote:
OK, I getting better with ER but I still don't have a clue about someFirst, run "cdr stop", just prior to taking the backup. As soon as you
things. I can't seem to make the following work:
I take a backup copy of an ER node with ER active and replicating. I
then restore it to another machine in stage. I am not using the same
instance name or group name when I restore. I was hoping to use the
backup to set up another test environment. I don't want the
environments to interfere with each other. I am using IDS 11.5 FC3.
It is a simple pitcher catcher arrangement. How do I get CDR to stop
replicating and redefine replication? Do I need to restore using the
same group name and instance name?
Thanks for any help. If you can point me to some good articles on ER I
would appreciate it. I have looked at a bunch of articles and it is
starting to sink in, but I have a few gaps in my knowledge.
start the backup and get the archive checkpoint, then you can run "cdr
start" to resume ER.
Then - when restoring the system to the test machine you can simply run
"cdr remove". That will remove the existing ER metadata and cleanup any
delete shadow tables.
do you mean "cdr delete" ?
When I type in "cdr remove" I get an error.
cdr remove
usage: cdr remove <object>
remove onconfig [-c server] OnconfigText
opps -
cdr delete server --force
The force option will allow removal of all of the metadata and the
shadow tables if ER is not running.
OK, I am really thankful for all of the help on this so far. I did:
1588 cdr delete server g_catcher_cr -c g_catcher_cr
1589 cdr list server
1590 sett monster1
1591 cdr list server
1592 sett monster4
1593 cdr delete server g_pitcher_cr
1594 cdr list
Monster4 being the source and monster1 being the target.
I change the group names in the sqlhost file and now I am getting:
+ cdr define server --connect=g_monster_catcher1 --ats=/usr/local/
informix_dev/cdr_logs/monster1/ATS --ris=/usr/local/informix_dev/
cdr_logs/monster1/RIS --idle=0 --leaf --init g_monster_catcher1
command failed -- no sync server (84)
Can not switch to syscdr sqlcode:-329+ exit
For some reason it doesn't seem to want to recreate the syscdr
database. Is there a bug in 11.5FC3? Or do I need to force it?
-329 Database not found or no system permission.
The database you tried to open is not visible to the database server.
Check the spelling of the name. Possibly the database is located in a
different database server (or network system), and you have omitted to
specify the server name (or site name) with the database name. If you
are sure the database should exist just as you spelled it, your next
step depends on the database server you are using.
If you are using IBM Informix SE, the visible databases are
directories
with names in the form dbname.dbs. You must be able to read from and
write to them. The database server looks first in the current working
directory and then in each directory named in the DBPATH environment
variable. The most common cause of this error is an incorrect setting
or no setting for the DBPATH environment variable.
If you are using IBM Informix Dynamic Server, IBM Informix Universal
Server, or
IBM Informix OnLine Dynamic Server, the database does not exist as you
spelled it.
In some environments, two or more instances of the database server can
run at
once and each instance has its own collection of databases. For
Version 6.0
and later, the value of the INFORMIXSERVER environment variable
determines the
instance of the database server that you use. For Versions 5.1x and
earlier,
the ONCONFIG environment variable points to the configuration file
that
determines the instance. See your database server administrator if you
think
you might be using the wrong instance.
If you are connected to a secondary database server, the database you
tried
to open might exist, but is not logged. Databases are required to be
logged
to be able to access them on secondary database servers.
.
- Follow-Ups:
- Re: ER question
- From: Madison Pruet
- Re: ER question
- References:
- ER question
- From: bozon
- Re: ER question
- From: Madison Pruet
- Re: ER question
- From: bozon
- Re: ER question
- From: Madison Pruet
- ER question
- Prev by Date: Re: ER question
- Next by Date: Re: ER question
- Previous by thread: Re: ER question
- Next by thread: Re: ER question
- Index(es):
Relevant Pages
|
