Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

How to sync syslogins in MSA?

5 posts in General Discussion Last posting was on 2011-11-29 06:25:17.0Z
Eisen Posted on 2011-11-23 02:53:58.0Z
Sender: 52b2.4ecb3f11.1804289383@sybase.com
From: Eisen
Newsgroups: sybase.public.rep-server
Subject: How to sync syslogins in MSA?
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4ecc6046.498e.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 22 Nov 2011 18:53:58 -0800
X-Trace: forums-1-dub 1322016838 10.22.241.41 (22 Nov 2011 18:53:58 -0800)
X-Original-Trace: 22 Nov 2011 18:53:58 -0800, 10.22.241.41
Lines: 17
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9094
Article PK: 870256

Dear all
Current I build a MSA system to replicate two user
databases, but since the db users modificated frequently on
the primary side, there always are the user issue in
transaction commit on replicate side like "user not
exists"...
I think if there's some solution to sync syslogins,
sysloginroles and syssrvroles beside manual operation? How
about adding the master db into MSA only for system
procedures? or just replicated these 3 tables by
table-replication? and if there some issue in RS or network,
would it make the syslogs in primary master unable to be
truncated and make disaster?
Thanks in advance for your help.

Best Regards
Eisen


Manish Negandhi [TeamSybase] Posted on 2011-11-23 03:30:39.0Z
From: "Manish Negandhi [TeamSybase]" <nospam_negandhi.manish@gmail.com>
Newsgroups: sybase.public.rep-server
References: <4ecc6046.498e.1681692777@sybase.com>
Subject: Re: How to sync syslogins in MSA?
Lines: 32
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3664
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4ecc68df$1@forums-1-dub>
Date: 22 Nov 2011 19:30:39 -0800
X-Trace: forums-1-dub 1322019039 10.22.241.152 (22 Nov 2011 19:30:39 -0800)
X-Original-Trace: 22 Nov 2011 19:30:39 -0800, vip152.sybase.com
X-Authenticated-User: teamsybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9095
Article PK: 870257

You can make use of master database replication, although it is limited to
DDL and the few system commands related to logins and roles it should work
in
the situation you mentioned. There is a good info and example given in the
link

http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc32511.1550/html/rsadmin_vol_1/BGBEDIGC.htm

-HTH
Manish Negandhi
[TeamSybase]

<Eisen> wrote in message news:4ecc6046.498e.1681692777@sybase.com...
> Dear all
> Current I build a MSA system to replicate two user
> databases, but since the db users modificated frequently on
> the primary side, there always are the user issue in
> transaction commit on replicate side like "user not
> exists"...
> I think if there's some solution to sync syslogins,
> sysloginroles and syssrvroles beside manual operation? How
> about adding the master db into MSA only for system
> procedures? or just replicated these 3 tables by
> table-replication? and if there some issue in RS or network,
> would it make the syslogs in primary master unable to be
> truncated and make disaster?
> Thanks in advance for your help.
>
> Best Regards
> Eisen


Eisen Posted on 2011-11-23 08:13:30.0Z
Sender: 52b2.4ecb3f11.1804289383@sybase.com
From: Eisen
Newsgroups: sybase.public.rep-server
Subject: Re: How to sync syslogins in MSA?
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4eccab2a.55e6.1681692777@sybase.com>
References: <4ecc68df$1@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 23 Nov 2011 00:13:30 -0800
X-Trace: forums-1-dub 1322036010 10.22.241.41 (23 Nov 2011 00:13:30 -0800)
X-Original-Trace: 23 Nov 2011 00:13:30 -0800, 10.22.241.41
Lines: 48
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9096
Article PK: 870258

Hi Manish
Thanks for your reply. Yes. I came here just after I read
it from manual. And I worry about it -- for obviously it
needs to configure the master db into the RS system, so the
syslogs segment maybe fullfilled if RS DSI down or replicate
side network issue (not the primary side network issue) and
can't be truncated and made the whole primary side down. And
the sample shows that the master replicate all the system
procedures -- I don't know if it would replicate other
system procedures like sp_diskdefault...

Best Regards
Eisen

> You can make use of master database replication, although
> it is limited to DDL and the few system commands related
> to logins and roles it should work in
> the situation you mentioned. There is a good info and
> example given in the link
>
>
http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc32511.1550/html/rsadmin_vol_1/BGBEDIGC.htm
>
> -HTH
> Manish Negandhi
> [TeamSybase]
>
> <Eisen> wrote in message
> > news:4ecc6046.498e.1681692777@sybase.com... Dear all
> > Current I build a MSA system to replicate two user
> > databases, but since the db users modificated frequently
> > on the primary side, there always are the user issue in
> > transaction commit on replicate side like "user not
> > exists"...
> > I think if there's some solution to sync syslogins,
> > sysloginroles and syssrvroles beside manual operation?
> > How about adding the master db into MSA only for system
> > procedures? or just replicated these 3 tables by
> > table-replication? and if there some issue in RS or
> > network, would it make the syslogs in primary master
> > unable to be truncated and make disaster?
> > Thanks in advance for your help.
> >
> > Best Regards
> > Eisen
>
>


"Mark A. Parsons" <iron_horse Posted on 2011-11-23 15:21:36.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.rep-server
Subject: Re: How to sync syslogins in MSA?
References: <4ecc68df$1@forums-1-dub> <4eccab2a.55e6.1681692777@sybase.com>
In-Reply-To: <4eccab2a.55e6.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4ecd0f80$1@forums-1-dub>
Date: 23 Nov 2011 07:21:36 -0800
X-Trace: forums-1-dub 1322061696 10.22.241.152 (23 Nov 2011 07:21:36 -0800)
X-Original-Trace: 23 Nov 2011 07:21:36 -0800, vip152.sybase.com
Lines: 67
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9097
Article PK: 870259

Take a look at RS Admin Guide #2; somewhere around page 66 is a section titled "Supported DDL commands and system
procedures" - the second half of the list shows the DDL/procs that can be replicated from the master database.

You'll notice that the only DDL/procs supported (for replication) in the master database are related to logins and roles
... the basic stuff you need to keep your logins in sync between 2 dataservers.

If you wish to further restrict what's replicated from the master database you could use MSA replication (for the master
database) and adjust the database repdef to include/exclude DDL or include/exclude specific procs.

---------

If you're a glutton for punishment you can roll your own code to replicate select procs from the master database. Rob's
still got a copy of my Techwave2000 presentation on his site (http://www.sypron.nl/markaparsons.zip) that's based on
work I did in 1996-1997 on master database replication. While this method still works it does require an ongoing effort
to keep it up to date (eg, reload custom procs after each run of the installmaster script; update custom procs as
Sybase-supplied procs change over time).

On 11/23/2011 03:13, Eisen wrote:
> Hi Manish
> Thanks for your reply. Yes. I came here just after I read
> it from manual. And I worry about it -- for obviously it
> needs to configure the master db into the RS system, so the
> syslogs segment maybe fullfilled if RS DSI down or replicate
> side network issue (not the primary side network issue) and
> can't be truncated and made the whole primary side down. And
> the sample shows that the master replicate all the system
> procedures -- I don't know if it would replicate other
> system procedures like sp_diskdefault...
>
> Best Regards
> Eisen
>
>
>> You can make use of master database replication, although
>> it is limited to DDL and the few system commands related
>> to logins and roles it should work in
>> the situation you mentioned. There is a good info and
>> example given in the link
>>
>>
> http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc32511.1550/html/rsadmin_vol_1/BGBEDIGC.htm
>>
>> -HTH
>> Manish Negandhi
>> [TeamSybase]
>>
>> <Eisen> wrote in message
>>> news:4ecc6046.498e.1681692777@sybase.com... Dear all
>>> Current I build a MSA system to replicate two user
>>> databases, but since the db users modificated frequently
>>> on the primary side, there always are the user issue in
>>> transaction commit on replicate side like "user not
>>> exists"...
>>> I think if there's some solution to sync syslogins,
>>> sysloginroles and syssrvroles beside manual operation?
>>> How about adding the master db into MSA only for system
>>> procedures? or just replicated these 3 tables by
>>> table-replication? and if there some issue in RS or
>>> network, would it make the syslogs in primary master
>>> unable to be truncated and make disaster?
>>> Thanks in advance for your help.
>>>
>>> Best Regards
>>> Eisen
>>
>>


Eisen Posted on 2011-11-29 06:25:17.0Z
Sender: 7f2d.4ed47a40.1804289383@sybase.com
From: Eisen
Newsgroups: sybase.public.rep-server
Subject: Re: How to sync syslogins in MSA?
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4ed47acd.7f99.1681692777@sybase.com>
References: <4ecd0f80$1@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 28 Nov 2011 22:25:17 -0800
X-Trace: forums-1-dub 1322547917 10.22.241.41 (28 Nov 2011 22:25:17 -0800)
X-Original-Trace: 28 Nov 2011 22:25:17 -0800, 10.22.241.41
Lines: 88
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9098
Article PK: 870260

Hi Mark
Thanks a lot for your help. After testing, RS really
works fine on replicating system procedures in master
databases. Thanks again.

Best Regards
Eisen

> Take a look at RS Admin Guide #2; somewhere around page 66
> is a section titled "Supported DDL commands and system
> procedures" - the second half of the list shows the
> DDL/procs that can be replicated from the master database.
>
> You'll notice that the only DDL/procs supported (for
> replication) in the master database are related to logins
> and roles .... the basic stuff you need to keep your
> logins in sync between 2 dataservers.
>
> If you wish to further restrict what's replicated from the
> master database you could use MSA replication (for the
> master database) and adjust the database repdef to
> include/exclude DDL or include/exclude specific procs.
>
> ---------
>
> If you're a glutton for punishment you can roll your own
> code to replicate select procs from the master database.
> Rob's still got a copy of my Techwave2000 presentation on
> his site (http://www.sypron.nl/markaparsons.zip) that's
> based on work I did in 1996-1997 on master database
> replication. While this method still works it does
> require an ongoing effort to keep it up to date (eg,
> reload custom procs after each run of the installmaster
> script; update custom procs as Sybase-supplied procs
> change over time).
>
>
> On 11/23/2011 03:13, Eisen wrote:
> > Hi Manish
> > Thanks for your reply. Yes. I came here just after I
> > read it from manual. And I worry about it -- for
> > obviously it needs to configure the master db into the
> > RS system, so the syslogs segment maybe fullfilled if RS
> > DSI down or replicate side network issue (not the
> > primary side network issue) and can't be truncated and
> > made the whole primary side down. And the sample shows
> > that the master replicate all the system procedures -- I
> > don't know if it would replicate other system procedures
> like sp_diskdefault... >
> > Best Regards
> > Eisen
> >
> >
> >> You can make use of master database replication,
> although >> it is limited to DDL and the few system
> commands related >> to logins and roles it should work in
> >> the situation you mentioned. There is a good info and
> >> example given in the link
> >>
> >>
> >
>
http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc32511.1550/html/rsadmin_vol_1/BGBEDIGC.htm
> >>
> >> -HTH
> >> Manish Negandhi
> >> [TeamSybase]
> >>
> >> <Eisen> wrote in message
> >>> news:4ecc6046.498e.1681692777@sybase.com... Dear all
> >>> Current I build a MSA system to replicate two user
> >>> databases, but since the db users modificated
> frequently >>> on the primary side, there always are the
> user issue in >>> transaction commit on replicate side
> like "user not >>> exists"...
> >>> I think if there's some solution to sync syslogins,
> >>> sysloginroles and syssrvroles beside manual operation?
> >>> How about adding the master db into MSA only for
> system >>> procedures? or just replicated these 3 tables
> by >>> table-replication? and if there some issue in RS or
> >>> network, would it make the syslogs in primary master
> >>> unable to be truncated and make disaster?
> >>> Thanks in advance for your help.
> >>>
> >>> Best Regards
> >>> Eisen
> >>
> >>