Hi there.
I'm starting to arrange a replication server at test environment, and
as I already have the same scenary at produciton, a primary ( venus )
and a replication ( mars ) servers, I just copied the /sybase/
REP-12_5/ folder from the replication server, and tried to run the
rs_init to configure, this way:

/sybase > . ./REP-12_5/SYBASE.sh
/sybase > echo $SYBASE
/sybase/REP-12_5
/sybase >

Then
/sybase/REP-12_5/install > rs_init
but it's failing and I don't know why:
brutusrep:/sybase > /sybase/REP-12_5/install/rs_init
The SYBASE environment variable is being temporarily reset to '/
sybase' because rs_init is being invoked from that directory.


The context allocation routine failed when it tried to load
localization files!!
One or more following problems may caused the failure

Your sybase home directory is /sybase. Check the environment variable
SYBASE if it is not the one you want!
Cannot access file /sybase/config/objectid.dat
Could not allocate context structure in syb_system_default_charset().


The context allocation routine failed when it tried to load
localization files!!
One or more following problems may caused the failure

Your sybase home directory is /sybase. Check the environment variable
SYBASE if it is not the one you want!
Cannot access file /sybase/config/objectid.dat
Could not allocate context structure in syb_system_default_language().


The context allocation routine failed when it tried to load
localization files!!
One or more following problems may caused the failure

Your sybase home directory is /sybase. Check the environment variable
SYBASE if it is not the one you want!
Cannot access file /sybase/config/objectid.dat
INTERNAL ERROR: Unable to load messages for product 'sybinit' using
language 'us_english' and character set 'iso_1': could not locate the
localization file '/sybase/locales/us_english/iso_1/sybinit/
sybinit.loc'.
Please make a note of this error and contact your Sybase
representative.
INTERNAL ERROR: Unable to initialize the Localization Manager.
Please make a note of this error and contact your Sybase
representative.
Exiting.


Any ideas?

Solaris 8
ASE 12.5.4
REP-12.5
Thanks
Guto.

On Aug 5, 9:39*pm, Guto <gutom... (AT) gmail (DOT) com> wrote:
Hi Guto

If I understand you properly, you have copied only /sybase/REP-12_5
directory. If so - this is insufficient, you should copy the whole /
sybase directory (but not any datafiles or stable queues in case if
you created it under /sybase). Replication server (RS) needs Open
Client components in order to function properly. If, for some reason,
you can't copy the whole /sybase directory then, at the very minimum,
RS needs following directories/files under /sybase in order to
function properly:

charsets
collate
config
interfaces
locales
OCS-12_5
SYSAM-1_0

Of course, installing RS with EBF from scratch with installer is the
best option.

Hope it helps
Leonid Gvirtz
http://www.gvirtz-consulting.com

On 6 ago, 04:47, Leonid Gvirtz <lgvi... (AT) yahoo (DOT) com> wrote:
Hi Leonid Thanks for your answer..

Let me clarify what I did.
This machine to where I copied the the REP-12-5 folder, already have
a
Sybase instance running, I just want to transform it into a
replicattion server.

Under /sybase I have:
sybase_125 -> the test database, up and running which will be turned
into a replication one.
REP-12_5 -> directory I copied from the production environment, where
I have the same structure that I'm trying to do at test.

AT PRODUCTION:

VENUS ( primary ) replicate to -> MARS ( replication server )

AT TEST:

JUPITER ( independant server, its data became from periodic MARS
databases dumps )
SATURN ( independant server, its data became from periodic MARS
databases dumps )

What I'm trying to do on test:

JUPITER( PRIMARY ) replicate to > SATURN ( REPLICATION SERVER )

JUPITER and SATURN used to be independent test databases, on where I
load the MARS dump, as needed.
As I decided to have exactly the same production environment at test,
I'm willing to
transform SATURN into a replication server for JUPITER. In both
machines I have the all MARS databases loaded.
So I thought that a good start will be to copy the REP12_5 from MARS
and run the rs_init in order to configure it as a
replication server.

But when I run /sybase > REP-12_5/install/rs_init, even if I run the
SYBASE.sh I have this error regarding the $SYBASE environment
variable.

Hope this clarify my situation here.
Thanks!

On Aug 6, 3:45*pm, Guto <gutom... (AT) gmail (DOT) com> wrote:
Hi Guto

I'm still not completely sure what happens on SATURN right now (is the
structure of directories equal to what you have on MARS?), but I think
that the best solution in this situation is to copy the whole existing
SYBASE installation from MARS (with RS) to a dedicated directory on
SATURN, such as /sybase_rs125, and use a dedicated OS user to run RS
on SATURN, this way you will prevent any possible conflicts between RS
and the existing ASE.

I remember that I encountered a conflict between charset/locale
related files of ASE and RS 12.5 in the past. Without installation of
charset/locale-related files that come with RS, rs_init and may be
other RS components didn't work properly. In addition, RS 12.5 (quite
an old version, by the way) uses OpenClient 12.5, while ASE 12.5.4
uses OpenClient 12.5.1 - another possible source of conflict.
Additional advantage of separation between ASE and RS installations is
that future upgrades of ASE/RS will not affect other SYBASE
installations on the server at all.

Also, from the message that you receive from rs_init:
---The SYBASE environment variable is being temporarily reset to '/
---sybase' because rs_init is being invoked from that directory.

I can conclude that $SYBASE environment variable is probably not set,
I'm able to reproduce this message on my environment if I unset
$SYBASE and try to run rs_init, so please check your environment
variables.

Hope it will help you to solve the problem
Leonid Gvirtz
http://www.gvirtz-consulting.com