creating a rep server using rs_init

Hi All.

We have installed Replication server 12.0 in the same directory as ASE 12.5.4. We have 2 servers A and B both at 12.5.4. I am trying to setup the replication server using rs_init. RSSD is created on B. When I run the rs_init, I am getting this error:

Open Client Message:
Message number: LAYER = (5) ORIGIN = (3) SEVERITY = (5) NUMBER = (131)
Message String: ct_init(): network packet layer: internal net library error: Attempt to load protocol driver failed
CONNECTIVITY ERROR: Initialization of sybinit connectivity module failed.
INTERNAL ERROR: Unable to initialize the SQL Execution Module.


Please let me know how to resolve this error. Please let me know if any other info is required.

Who is Participating?
Joe WoodhouseConnect With a Mentor Principal ConsultantCommented:
> We have installed Replication server 12.0 in the same directory as ASE 12.5.4.

That's your problem. I'm pretty sure the docs say not to do that. The problem is both products are looking for Open Client files and will get confused if they're under the same top-level $SYBASE directory. Note you are getting Open Client errors.

Strongly suggest you instead maintain multiple top-level directories, and either have different logins using each directory, or a script that resets $SYBASE and other environment variables depending on which directory you're using. (Multiple logins is less prone to errors.)

Depending on the order you installed things you may also have caused problems for your ASE, although ASE 12.5 is less sensitive to this than RS 12.0 is.

By the way you really need RS 12.6 in this scenario as you won't have all ASE 12.5.x features supported on anything less than RS 12.5, and RS 12.6 is a vast improvement on RS 12.5 (internal commit control and SMP are two features you almost certainly want).

Sorry, I bet this isn't the answer you were hoping for.
Joe WoodhousePrincipal ConsultantCommented:
Hi. Sorry I didn't have a happier answer for you. I also have struggled with this exact same issue and even with profiles or different logins it is difficult to make RS and ASE play together in the same directory. Even when both products have the same versions I have seen applying an ASE EBF break RS because it patched Open Client stuff RS was using.

The only way I've ever had it work is to:

1) Have both ASE and RS at the same or "best fit" versions (ie ASE 12.5.x and RS 12.6.x as above)
2) Always install RS last
3) Always patch RS last

It really is a lot simpler to have them in separate directories, for all that that's quite a nuisance.

I can't comment on whether they play together any more nicely when both are at the 15.0.x levels, I haven't yet had occasion to try that.

Good luck!
cs2468Author Commented:
Hi ,

I did copy the RS 12.0 to the directory which had ASE 12.0 and I changed the .profile to point to the 12.0. But now, it is giving this error:

Unable to obtain information about file system ''.  Operating system returned: No such file or directory.
INTERNAL ERROR: Format error in localization file '/export/home/sybase_old/sybase/locales/us_english/iso_1/sybinit/rs.loc': could not find 'sybinitmsg' section.  Aborting language load.
Attribute 'rs_diskp_name' could not be set because 'syb_queue' is an invalid value.

Please let me know if you need any other info  like the resource file used for rs_init.

Joe WoodhousePrincipal ConsultantCommented:
That error is saying it can't localise the environment (it doesn't know what language and character set to use to talk to you). That says it's still having problems resolving the correct environment variables. I can't tell which exactly is missing but something isn't right in the profile, at least one of the required environment variables aren't set or correct.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.