Sybase数据库技术，数据库恢复专家

ra_helpdevice is incorrect if the device is

stored under ASM.

datatypes are returned for varchar(max), nvarchar(max), and varbinary(max)

datatypes.

Workaround: Ensure that the replication agents in your replication environment

are version 15.1 ESD #1.

with error: "ChainedOperationException: Could not

concatenate chained operation because: Error

processing record with supplemental data whose

column index duplicates other data columns".

Workaround: use direct connection to repository

parameter is set to a value that does not

contain an underscore, Replication Agent will

create system objects with delimited names

in the primary database during initialization.

This may cause Replication Agent api commands

to fail.

NULLPointerException when attempting to read

a redo log on an AIX raw device.

when the database is inactive with respect to

replicated changes, even after reading to the end

of a log file or when reading at the end of the

log.

unexpectedly in its attempt to log an

error message. This can occur when

specific internal resources are not

available during the process of logging

the error message.

'ra_config pdb_archive_remove, true' fails with

exception "Could not find Resource Bundle

containing index: LR_BAD_ARC_DIR_ACCESS_WRITE".

case-sensitive replicate table name correctly.

may suspend and not terminate. This can

occur if 'rs_init' fails to properly

spawn a Replication Server process.

during DDL replication with error "The object whose id is

XXX is not a valid object." after the Replication

Agent has been re-initialized.

the 'assign action' values should be set

to 'warn' rather than

'stop_replication'.

immediately follows the insertion of an empty LOB

in the same location, fails with an error in

Replication Server indicating "The data row that

the writetext command is associated with is

missing."

infinite loop when executing the 'resume

connection skip transaction' command

which may cause the complete consumption

of RSSD log space or ASE locks. This

can occur if the ASE and the Replication

Server are both configured with

multi-byte character sets.

Daylight Saving Time transition are incorrectly

adjusted by one hour.

to Replication 15.0 or higher, an

'assign action' value is incorrectly

created for ASE error #41880 rather than

#418801.

lr_ntext_byte_order is hidden, and can not be

set by user.

could fail yet still allow the

associated transaction to incorrectly

commit. This can occur when the failure

is caused by insufficient ASE procedure

cache.

Initial testing:

PDM file 22.1 MB

Proxy(TBONE server):

Consolidation: 36 minutes

Extraction: 14 minutes

No proxy(TBONE server):

Consolidation: 20 minutes

Extraction: 13 minutes

during Daylight Saving Time transition are

incorrectly adjusted by one hour.

Daylight Saving Time transition are

incorrectly adjusted by one hour.

Support ASE dump transaction command with

parameter "standby_access".

operations because there is no object information

in the LogRecord" occurred against an "ALTER

PROCEDURE ... COMPILE" command issued against a

procedure whose owner is in the Replication

Agent's owner filter list.

allowed by the license, the Replication

Server will incorrectly start rather

than terminate. This can occur only

when using an un-served license.

IllegalStateException if Replication

Agent is never resumed.

mark all user tables in the primary database.

*** glibc detected *** corrupted double-linked list: 0x08a0d908 ***

Theses errors occurs on RS126E6 when the standby side of replication is stopped when data is being replicated.

will generate a DSI 32058 error in Replication

Server with a length mismatch. The error is

similar to "The value given for

'<repdef name>.<encrypted column name>' cannot be

translated from datatype 'binary' to the required

datatype 'varbinary'. Value length is '33';

Maximum target length is '11'."

key violation at the replicate database because

an insert rolled back at the primary database is

incorrectly replicated.

time an SQM callback is executed.

Although this is a valid state for the

RSI internal list, the SQM callback is

unprepared for this state which can

result in a failure of the SQM.

"Replication Definition Not Found" Exception may

occur if a table is re-marked for replication

using the pdb_setreptable command. Table is marked

once with the "owner" keyword and once without the

"owner" keyword.

with error "The date time string is invalid and

can not be parsed correctly."

with error: "ChainedOperationException: Could not

concatenate chained operation because: Error

processing record with supplemental data whose

column index duplicates other data columns".

with a NullPointerException on a 'resume' command

when the owner of the primary database can not be

found in sys.sysusers view.

a table when a synonym is passed as a parameter

in session repository version locators prevents

truncation.

function replication if the primary

function name and the replicate function

name differ.

Two new Replication Agent commands:

"ra_deviceoffset", "ra_helpdeviceoffset"

ra_deviceoffset

Description

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

Note This command is available only for Oracle.

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

Changes the raw disk device read offset for a

log device recorded in the RASD.

Syntax

ra_deviceoffset device_id, device_offset

Parameters

device_id The device ID is the Oracle redo log

"Group number".

device_offset The offset of the raw device,

from which Replication Agent starts log scan.

Examples

ra_deviceoffset 1, 20

This command specifies the raw device read off-

set to the log device ID "1" as: 20.

Usage

- When ra_deviceoffset is invoked, Sybase Replica-

tion Agent records the specified raw device read

offset for the specified log device in the RASD.

- To get information about log devices stored in

the RASD, use the ra_helpdevice command.

- When ra_updatedevices is invoked, device offset

will not be reset to default value.

The default device read offset is zero.

- If ra_deviceoffset is invoked when the Sybase

Replication Agent instance is in Replicating

state, it returns an error.

- The ra_deviceoffset command is valid only

when the Sybase Replication Agent instance is

in Admin state.

See also

ra_helpdeviceoffset, ra_devicepath,

ra_helpdevice, ra_updatedevices

ra_helpdeviceoffset

Description

Note This command is available only for Oracle.

Returns device offset information about primary

database log devices from the RASD log device

repository.

Syntax

ra_helpdeviceoffset [device]

Parameters

device

The device ID of the primary database log device.

Examples

Example 1

ra_helpdeviceoffset

This command returns device offset information

about all primary database log devices recorded

in the log device repository.

Example 2

ra_helpdeviceoffset 1

This command returns information about the pri-

mary database log device ID "1" in the log

device repository

Usage

- The ra_helpdeviceoffset command returns the

following information for each primary database

log device recorded in the RASD:

Device ID - the log device ID defined by the

primary data server.

Note For Oracle, the ID is the value of the

Oracle Redo Log Group to which this file

belongs.

Database name - the name of the primary

database associated with the log device.

Device name - the logical name of the log

device defined by the primary data server.

Server device path - the path to a multi-

plexed version of the log device.

Disk device path - the path to the log

device (at the standby site).

Disk device offset - the offset from which

Sybase Replication Agent starts scan Oracle

redo log in the log device. The value of

device offset displayed is the value of

"raw_device_offset" property in the Rep-

lication agent configuration file plus the

offset value set by command "ra_deviceoffset".

Disk device status - the current status of

the server device path (ACCESSIBLE, NOT_VALID,

or OPEN).

- The disk device path is the current value

recorded in the RASD. Sybase Replication Agent

uses the disk device path recorded in its RASD

to find each log device.

- For each log device recorded in the RASD, you

can set or change the disk device path with the

ra_devicepath command and set or change the

device offset with the ra_deviceoffset command.

- If you do not specify a disk device path (using

ra_devicepath), the value recorded for the disk

device path is DEFAULT, and Sybase Replication

Agent uses the value recorded for the server

device path to find the log device.

- The disk device status is updated by the Log

Reader component each time you invoke the

ra_helpdeviceoffset command.

- If ra_helpdeviceoffset is invoked with no option,

it returns information for all log devices

recorded in the RASD log device repository.

- If ra_helpdeviceoffset is invoked with the device

option, it returns information only for the

specified log device.

- The ra_helpdevice command is valid when the

Sybase Replication Agent instance is in

either Admin or Replicating state.

See also

ra_deviceoffset, ra_helpdevice,

ra_updatedevices

when set to false, sends all before column images

regardless of columns identified in the

associated Replication Definition.

scanning stops replication.

synonym, no information was given back when you

try to query marked table through its synonym.

a SQLException error when invoking the ra_migrate

command.

file processing fails with the error

"Device <+XYZ> does not exist" when the parameter

"pdb_archive_path" is set to an ASM disk group

name.

procedure to add new arguments, an

"Unsupported SQL type 1111" error occurs.

with the Replication Server, (2) an MSA database

is also registered with the Replication Server

and (3) a replication definition is created for

a table in the warm standby database, then the

active connection to the warm standby database

cannot be dropped even after the replication

definition has been successfully dropped.

Server causes Replication Agent to go to ADMIN

state with an error similar to

"com.sybase.jdbc3.jdbc.SybSQLException: Line 1,

character 120: Incorrect syntax with the keyword

'_bf'" because a delete operation row has all

NULL data fields.

populates an RSSD table with the value 'set

computed_dml on'. The correct value is 'set

dml_on_computed on'.

Resume failure may happen when executing

'pdb_xlog move,force' before 'pdb_init'

and 'ra_init'.

In case of this failure, please issue

command 'pdb_init move_truncpt' to reset

truncation point and 'resume' MRA again.

VirtualFileNotFoundException error is thrown after

the primary database is restored.

to replicate after the following sequence of steps:

1. Create a stored procedure and mark it for

replication.

2. Unmark and drop the stored procedure

3. Re-create the procedure with the same name,

mark, execute it.

processing, the article's version in the RASD is

not correctly updated which may cause some

operations to be missed when Replication Agent

re-scans the log.

reports 'Segments Allocated' for the new partition as '1' if the stored procedure is invoked without parameters. If the stored procedure is invoked with the new partition name as the parameter, the 'Segments Allocated' field is correctly reported as '0'.

does not return the value for the

'dsi_alt_writetext' parameter.

incorrectly marked for replication.

Support migration to mra151.

can not be automatically created for a table with

a column containing 'sysname' datatype.

the ability to read redo logs that are mirrored

and also remain replicating if it cannot connect

to ASM when attempting to refresh log devices.

pdb_setreptable can not

recognize tables with long

names having '_' and '%'.

The length of table name cannot

exceed 255.

replicating due to an error. The error log

displays an error similar to:

"ChainedOperationException: Could not set header

to operation... because the chained operation

header.... is already set."

The error is caused by a failure to handle a

rollback operation applied to one log operation

of a chained operation.

java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0

Size: 6" occurred with primary Oracle multi-block

undo enabled.

Update consolidation adds the latest frozen version of the document in addition to the document version you added first as a configuration member.

pdb_date can not return

the correct month infomation

if OS regional is Chinese.

thrown when replicating nested UDD type.

to replicate commands whose log record "Flag Bits"

are set to value 3600.

rollback record to Replication Server that

incorrectly removes the begin transaction record,

causing Replication Server to fail with error:

"#9022 DIST Cannot deliver a command since no

transaction is open".

table, or to add or delete columns, a

NullPointerException occurs.

'Custom' and then decides to navigate backwards to choose a different

installation type, the component subset is not properly changed to match

the installation type.

Customer's description:

Currently, PD keeps track of the changes we make at the object level and automatically places check marks next to the updates that we have initiated when consolidating with the repository. However, if there are multiple changes to the same object, PD shows all the changes and we have to select which attribute changes that we have generated. We need PD to keep track of the changes down to the attribute level and automatically check only those changes at the attribute level that we have initiated. We realize that this can be done by manually modifying the check boxes at the attribute level; however, when you have a team of 8 people working on the same model and updating the same requirements, (modifications from a review perspective, modification from a consistency perspective and modifications from a content perspective), the number of modifcations is great and the time that it takes to step through each individual attribute is extensive. Fixing this would greatly reduce people clobbering eachother's work.

with the Linux 'libXp' package by default. If the Linux 'libXp' package

is missing, the RS 1510 GA and RMP 1510 GA 'setup' installation command

will fail and the following generic message is generated ...

The installer is unable to run in graphical mode. Try running

the installer with the -console or -silent flag.

If the 'setup' installation command is invoked with the following

parameters ...

setup -is:javaconsole -log '#' @ALL

... this additional message is generated ...

Install.product.install,

com.installshield.wizard.StandardWizardListener,

dbg,

java.lang.UnsatisfiedLinkError:

/mnt/cdrom/JVM/bin/libawt.so:

libXp.so.6:

cannot open shared object file:

No such file or directory

To resolve this issue, install the Linux 'libXp' package. This can be

done on Redhat Enterprise Linux with the following command ...

yum install libXp

ra_maintid command throws NullPointerException

after Replication Agent is initialized.

pdb_get_tables and pdb_get_procedures

can not recognize table/procedure

with long names having '_' and '%'.

The length of table/procedure name

cannot exceed 255.

correctly calculate the rollback point for a

"rollback to save point" operation. The failure

to rollback some operations causes an eventual

'duplicate key' violation at the replicate

database.

replicate owner when the replication definition

is created automatically and when it is created

for replicating Oracle to ASE.

A new property "rs_replicate_owner_required"

allows Replication Agent to always supply the

owner in the replicate table name when the

replication definition is generated.

rs_replicate_owner_required

Description:

Determines if the owner should always be supplied

in the replicate table name when the Replication

Agent generates replication definitions, so that

Replication Server can distinguish between

replicate tables of the same name with different

schema/owner, and different schema/owner than the

replicate maintenance user applying the command.

Default:

true

Values:

true � The owner will always be included in the

replicate table name of generated replication

definitions.

false � The owner will only be included in the

replicate table name of generated replication

definitions if the primary name is also owner

qualified.

Comments:

- When the rs_replicate_owner_required is set

to true, generated replication definitions will

always be created with the replicate owner

and table name in the "with replicate table

named" clause.

Example:

create replication definition ra$0xca61_MyTable

with primary at rao.ora10g

with primary table named 'MyTable'

with replicate table named 'MyOwner'.'MyTable'

(

"QUANTITY" rs_oracle_decimal,

"ORDER_NUMBER" varchar(200)

)

primary key( "QUANTITY","ORDER_NUMBER" )

searchable columns( "QUANTITY","ORDER_NUMBER" )

send standby all columns

replicate minimal columns

- When the rs_replicate_owner_required is set

to false, generated replication definitions will

be created with the replicate owner

and table name in the "with replicate table

named" clause only if the primary table is

owner qualified.

Example:

create replication definition ra$0xca61_MyTable

with primary at rao.ora10g

with primary table named 'MyTable'

with replicate table named 'MyTable'

(

"QUANTITY" rs_oracle_decimal,

"ORDER_NUMBER" varchar(200)

)

primary key( "QUANTITY","ORDER_NUMBER" )

searchable columns( "QUANTITY","ORDER_NUMBER" )

send standby all columns

replicate minimal columns

state with error "Error processing

record with supplemental data whose column index

duplicates other data columns."

did not reflect the correct product

catagory 'Mirror Replication Agent'

but always refer to 'Replication Agent'

Oracle 9i because the Replication Agent does not

correctly recognize the desired archive redo log.

The error is similar to "An Archive file was not

found. Reason: Archive log file for LSN <xxx> is

not found. File <archiveLog>.

new version. As a result, there are no fixed

bugs to list in this section.

the primary database can be inappropriately

replicated when a rollback occurs in the middle

of several concurrent transactions.

rs_oracle_datetime when a year value exceeds 4712.

convert an Oracle date value when the year

portion of the date value is larger than 4712.

Also, the installer for Replication Manager 15.1 does not display a confirmation message to create a new directory if the target installation directory does not exist.

with force option causes three Replication Agent

internal tables to be marked for replication and

associated replication definitions are created.

Unexpected replication definitions for rs_marker

and rs_dump are also created when

'rs_create_repdef all' command is issued.

RS using RS 15.0 or higher to a

replicate RS using RS 12.6 or earlier.

This can occur when the primary RS is

upgraded from RS 12.6 or earlier to RS

15.0 or later and the site version for

the primary RS is set to 1500.

the debug-log file shows following just before the proxy crashes

2008-06-03.15:24:30.000719 warning - SClient::OnAccept: too many clients

a DDL command that recompiles a procedure. The

error is similar to "Failed to handle the DDL

operations because there is no object

information in the LogRecord."

are not skipped because the pdb_skip_op command

interface does not take into account Oracle

SUBSCN field values.

Description

This command is available only for Oracle and

Microsoft SQL Server.

Returns, adds, or removes record identifiers from

a list of records to skip in processing. The

format of the identifier is database-specific.

To support RAC, log location and truncation is

done by System Change Number (SCN) instead of

Record Address (RBA). The skip operations feature

must be familiar with SCNs and thread numbers to

truncate the skip operations list and to skip the

correct operation across multiple threads.

Syntax

pdb_skip_op [ add , identifier ]

pdb_skip_op [ remove, { identifier | all } ]

Parameters

add

Adds a specified ID to the list of

identifiers of records to skip.

remove

Removes a specified ID from the list of

identifiers to skip.

identifier

Identifies the log record to skip. The syntax

allows for either an operation locator or a

database-specific identifier.

all

Allows you to remove all IDs in the

list of identifiers to skip.

Examples

Example 1

pdb_skip_op

This command with no parameters returns a list of

the identifiers for the records you want to skip.

Example 2

pdb_skip_op add, id

This command adds an ID to the list of identifiers

you want to skip.

Example 3

pdb_skip_op remove, id

To remove an ID to the list of identifiers you

want to skip.

Example 4

pdb_skip_op remove, all

This command removes all the IDs from the list of

identifiers you want to skip.

Usage

- The pdb_skip_op command allows you to skip

problem records, thereby avoid having to

re-initialize the Replication Agent.

- Skipped records are written to the system log

as a warning message.

- The pdb_skip_op command is valid when the

Replication Agent is in Admin state.

- The format of the generic identifier

is the 64 character LTM locator representing the

operation to skip.

- The format of the database-specific identifier:

- For Microsoft SQL Server, the identifier is

Log Sequence Number (LSN) and it has the

following form:

virtualfileseqno:pageid:operationsseqno

where:

- virtualfileseqno is the virtual

log sequence number.

- pageid is the page number.

- operationsseqno is the sequence

number of the operation.

You can get the LSN using the Microsoft

SQL Server DBCC command, or you can parse

it from the locator. For example:

- LSN in decimal format: �489:112:27�

- LSN in hexadecimal format:

�0x00000489:00000112:0027�

- For Oracle, the identifier contains, SCN

(System Change Number), redo log thread, and

Record Byte Address (RBA) and it has the

following form:

wrap.base.sub, thread, lsn.blknum.blkoffset

where:

- wrap is the SCN wrap number.

- base is the SCN base number.

- sub is the SCN sub index.

- thread is the redo log thread number

that the operation occurred on.

- lsn is the RBA log sequence number.

- blknum is the RBA block number.

- blkoffset is the RBA offset into the

block where this record resides.

The values must be specified in the

pdb_skip_op command together, enclosed in

quotes, each item separated by a period.

For example:

'0000.012345678.0001', '1',

'0012.0000444.0000123'

All values can be described as a hexadecimal

by prefixing the identifier with an �0x� as

follows:

'0x000c.00001bc.000007b'

or

'0x0000.00BC614E.000A'

See also

ra_helplocator, ra_locator

error similar to "Oracle log scanner error ...

log record <> was not correctly sorted - locator

is not greater than previous log record locator".

during resume when the maintenance user specified

in Replication Server is not a valid user in

primary database.

with an error similar to: "Could not concatenate

chained operation because: Error processing

record with supplemental data whose column index

duplicates other data columns".

enabled, the operation issued by the maintenance

user may not be filtered by the Replication Agent.

containing column names that are not quoted on the

"replicate if changed" clause.

LTL command exception when the connection

to the Replication Server is lost.

to delete an instance, entering

'n' to cancel the delete operation

will display an incorrect message

"Successfully deleted instance

<Instance Name>."

if a customer moves the truncation point with pdb_xlog init, move_truncpt and the truncation point is moved past ddl...alter table...for example, then there are two options.

1) pdb_xlog init, force ... this will update the RASD in a wholesale manner

2) unmark and mark the individual table if the user knows they only changed one table

time the Replication Agent is de-initialized with

the force option.

repeatly will display a different error message

each time.

RS using RS 15.0.1 to a replicate RS

using RS 12.6. This can occur when the

primary RS is upgraded from RS 12.1.

thrown when resuming Replication Agent and the

'pdb_auto_create_repdefs' configuration property

is set to true.

sends the Replication Agent to ADMIN state.

an OutOfMemory exception if there are large

transactions done by the maintenance user.

contains TEXT columns that allows NULL

values, these columns will be missing

from an UPDATE statement's WHERE clause

if these UPDATE statements are applied

at the primary database by an RS

maintenance user.

Replication Agent to ADMIN state while reading a

log record without any supplemental metadata.

The error is known to occur with an Oracle

database configurations DB_2K_CACHE_SIZE=16M and

undo_tablespace equal to a tablespace with block

size 2048.

Oracle DDL command processing sends the

Replication Agent to ADMIN state.

"No replication definition found" error after a

unmarking a table which is previously marked

with a different replicate name.

directly after the Replication Agent is changed

to replicating state results in a

NullPointerException. The error is limited to a

RAC replication environment.

occurred during initialization of a change vector

sends the Replication Agent to ADMIN state.

Replication Agent doesn't enter the admin state

when the quiesce command is issued.

results in replicate database constraint

violation.

dropped via an alter table, a subsequent insert

on the table will fail to replicate because of

a column mismatch.

"Add Modified Documents in Workspace" is not reliable enough because model(s) may have already been saved locally prior to consolidation.

definition, two database subscriptions are

created using the 'with dump marker' clause, the

process of creating the second database

subscription will incorrectly not suspend the

associated DSI connection.

new version. As a result, there are no fixed

bugs to list in this section.

truncate all versions of the user.

message "The value '4290772992' can not be

converted into a signed integer."

There are new Replication Agent System Database

backup features for saving and restoring the

ASA database.

The Replication Agent System Database is now

automatically backed up when the transaction log

is re-initialized, so in the event an error

occurs while the transaction log is being

re-initialized, it can be restored to the state

it was before re-initialization started.

When the Replication Agent System Database is

backed up, the most recent database backup is now

saved in a repository backup directory with a

time-stamped name in the format

"yyyy-MM-dd_HH.mm.ss" before the ASA database is

backed up. The ASA database is still backed up in

the location specified by the "rasd_backup_dir".

In addition, the database backup files are not

automatically removed. A new feature is provided

for backup maintenance.

Example backup directory:

<INSTALL_DIR>\RAX-15_1\myRAO\repository\backup\

2008-07-24_15.41.10

Note:

The Replication Agent System Database can be

backed up manually using the "rasd_backup"

command, or will be backed up automatically

when the transaction log is re-initialized.

The "rasd_restore" command has been enhanced to

take advantage of the new backup features. In

addition to having the ability to restore from

the most recent ASA database backup, individual

backups can be selected for restore.

Command Description

rasd_restore

Description

This command is available only for Oracle and

Microsoft SQL Server.

Restores the RASD.

Syntax

rasd_restore [backup_name]

Parameters

backup_name

The name of the backup to restore from. If the

backup name is ommited, the most recent backup

is restored.

Examples

rasd_restore

This command with no parameters restores the RASD

from the most recent backup.

rasd_restore 2008-07-24_15.41.10

This command restores the RASD from the

2008-07-24_15.41.10 backup.

Usage

When rasd_restore is invoked, it starts the

restore process for the RASD.

Sybase Replication Agent looks for the most

recent RASD backup files in the directory

identified by the rasd_backup_dir configuration

parameter when no parameters are input.

Sybase Replication Agent restores from the

specified backup in the directory identified by

the rasd_backup_dir configuration parameter

a backup name is provided as a parameter

When you create a Sybase Replication Agent

instance, a RASD backup directory is created

automatically as part of the instance directory

structure. The default value of the

rasd_backup_dir parameter points to that

directory.

If you invoke rasd_restore when the Sybase

Replication Agent instance is in Replicating

state, it returns an error.

The rasd_restore command is valid only when the

Sybase Replication Agent instance is in Admin

state.

See also

rasd_backup, rasd_helpbackup, rasd_removebackup

There are two new Replication Agent commands for

managing Replication Agent System Database

backups. They are rasd_helpbackup and

rasd_removebackup.

rasd_helpbackup

Description

This command is available only for Oracle and

Microsoft SQL Server.

Displays a list of RASD backups

Syntax

rasd_helpbackup

Example:

1> rasd_helpbackup

2> go

RASD Backups

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

2008-07-24_15.41.10

2008-07-28_10.08.27

2008-07-28_10.09.29

2008-07-28_10.11.31

(4 rows affected)

Usage

When rasd_helpbackup is invoked, it displays a

list of RASD backups stored in the directory

identified by the rasd_backup_dir configuration

parameter when no parameters are input.

The RASD backups are named with the date and time

at which the backup was created.

See also

rasd_backup, rasd_restore, rasd_removebackup

rasd_removebackup

Description

This command is available only for Oracle and

Microsoft SQL Server.

Removes RASD backups

Syntax

rasd_removebackup [backup_name | all]

Parameters

backup_name

The name of the backup to remove.

all

A keyword that allows you to remove all

RASD backups.

Examples:

rasd_removebackup 2008-07-24_15.41.10

This command causes the backup named

2008-07-24_15.41.10 to be removed

1> rasd_removebackup 2008-07-24_15.41.10

2> go

RASD Backups removed

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

2008-07-24_15.41.10

(1 row affected)

rasd_removebackup all

This command causes all of the backups to be

removed.

1> rasd_removebackup all

2> go

RASD Backups removed

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

2008-07-28_10.08.27

2008-07-28_10.09.29

2008-07-28_10.11.31

2008-07-28_10.20.55

(4 rows affected)

Usage

When rasd_removebackup is invoked, it removes a

RASD backup stored in the directory identified by

the rasd_backup_dir configuration parameter.

When rasd_removebackup is invoked with the 'all'

keyword, it removes all RASD backup stored in the

directory identified by the rasd_backup_dir

configuration parameter.

When rasd_backup is invoked, the names of all

backups removed is displayed.

The RASD backups are named with the date and time

at which the backup was created.

See also

rasd_backup, rasd_restore, rasd_helpbackup

VERSION info with NULL value.

old versioned articles.

when only one of the cluster instances is active.

Replication Agent pdb_archive_path configuration

parameter contains no Oracle archive logs,

Replication Agent will go to ADMIN state with an

unexpected thread death exception.

parallel transactions with random rollback on

a table containing LOB column.

Attribute in CDM is a special small object that is related to a data item

In all places in PD, Attribute properties inherits from Data item

properties (data type, length, comment, etc...)

Currently CMR is not showing anything for Attribute.

old versioned users.

command with a username that doesn't exist in the

primary database fails with error "Command

<ra_helpuser> failed - Could not list metadata

for user <XXX> because: null".

As an example,

version 1 / branch 10/ branching version 1

is displayed 110.1 where you should read 1.10.1

in processing Oracle archive log files when

customer's batch application runs and creates

40+ gigabytes of archive log files.

configured to use Dynamic SQL, the DSI

connection will fail and shutdown when

attempting to replicate the UNIVARCHAR datatype.

stable device ... 0516-622 synclvodm: Warning, cannot write lv control block...

on AIX only when a stable device is created on a raw partition using just the minimum default syntax of...

create partition repro_part on '/dev/r11445073e' with size 60

..., then the unix commands of exportvg and importvg are attempted...this causes the following problem...

0516-622 synclvodm: Warning, cannot write lv control block data.

synclvodm: Logical volume 11445073d updated.

... and then the stable device fails to come back online and the customer had to call IBM to get it rebuilt...

fails to replicate empty text/image values.

upgrade fails due to Replication Agent

ra_xlog_system_ system table failing to

find dbo.ra_truncate_logs table.

locator value to Replication Server when

replicating DDL commands and the pdb_gen_id

configuration parameter is set to a non-zero value.

the installer will terminate prematurely with the following message ...

Assertion failed: so->so_hard_contents, file softobj.c, line 363

sh: 11794 Abort(coredump)

exception "Invalid state encountered processing

commit operation" when applying DML commands

to Oracle system table MGMT_* if they are

for an Index Organized Table.

state with the following OracleRuntimeException

error "The operation is not the first operation

in a chain and a chained operation is not active."

replicating a table that has an after update trigger

and the update trigger contains some DML operation

that is applied to another table.

the option 'dsi_alt_writetext' set to

'dcany', the Replication Server may

terminate unexpectedly. This can occur

when the Replication Server processes a

system transaction.

command, the command returns successfully.

to create a table level replication

definition results in incorrect data

being sent to Replication Server. The

incorrect data causes the Replication

Server DSI to go down.

correctly for a table with no replicate columns.

an incorrect error message when the owner

value passed to it is invalid.

an OutOfMemory exception if there are large

transactions done by the maintenance user.

inadvertently changes the case of data server name or database name in RSSD if the

case of names specified in the command do not match the case of names in RSSD.

<instance ID>', will fail due to an invalid

instance ID even when a valid instance ID is

provided. This is a byte-order issue that is

only observed on "little-endian" platforms.

value which is immediately followed by an

insertion of a null text value causes a

non-null value to be replicated to the

replicate database.

replicate a "rollback to savepoint" operation on a

table containing a LOB column.

"Could not stop database <repository

database name>" error message.

to 'dcany', Replication Server will fail to

replicate LOB data that is over 32KB in size.

generation for a table with OBJECT type fails in

Replication Agent 15.1 using Replication Server

15.0 version.

stable queue is defined on a raw device.

Replication Agent to ADMIN status after issuing

"sp_setrepcol qaz_ddl, null, do_not_replicate"

command in ASE.

(9.9999999999999999999999999999999999999e125)

of an Oracle float datatype is inserted into a

marked table, Replication Agent will go to

ADMIN state.

thrown randomly during replication.

in user-defined datatype fails

to replicate.

is incorrectly replicated as an empty string.

on RedHat Enterprise Linux 5.0 if LANG environment variable is ja_JP.eucJP or ja_JP.UTF-8.

Replication Server.".

user invokes pdb_setreptable command to query

a non-existing table.

'check' command fails without any

error code printed on sybfilter driver

manager console.

restarts with primary database offline.

files are removed even when

pdb_archive_remove is set to false.

replicated.

ADMIN state with the error: "Invalid block

id <xx, xx> specified on log device

<directory> with log sequence number

<xxx,xxx>" when trying to position the

log scanner.

implementation to help improve latency

and CPU utilization.

2000 tables in the primary database, executing a

pdb_setreptable command with 'all, mark' option

causes an OutofMemory exception.

"LTIException: Received unexpected exception

during LTI processing", but no indication of

which operation caused the problem is given.

when attempting to change configuration

pds_database_name, pds_host_name or

pds_port_number while a TNS connection

description is being used.

1.go to configuration

2. in the general tab, it shows 10 as default, change the max user to 1 and save it

3. go to server status tab, and click restart

after restart, the max user will show 1, but it still can be accessed by 10. only after restart the tomcat, only 1 user can login.

pds_dac_port_number property defined in the

response file is set to a value other than

USE_DEFAULT, Replication Agent fails during

initialization with error "The port number

specified for property <pds_dac_port_number>

value <nnnn> is already in use."

initialization is an ASM device, then trying to

set the disk mirror path to a non-ASM (i.e. file

system, raw) device fails, even though no error

is displayed.

if the database user, defined by configuration

parameter pds_username, has CREATE SEQUENCE

privileges.

replicate an MSSQL UPDATE statement containing

the MSSQL datatype 'varchar(max)', the

Replication Server incorrectly generates an

UPDATE statement without a WHERE clause.

spaces from 'varchar' values.

Only with ADMIN Rights we can see then Dependencies from models inside Repository to our Model in the local workspace. We can see the Objects with a red ball.

If we are connected as User with no admin rights it is not possible to get the information about this dependencies. But this should be possible also for our 'Non-Admin'-Users.

the 'move_truncpt' option fails with a

NullPointerException when it is executed before

the ra_init command.

LOB data for two tables that are affected

by the same transaction, a NullPointerException

can occur. This exception will cause the

Replication Agent to go to ADMIN state.

SQL Server after initializing Replication Agent

for the first time.

non-ASE replicate databases, batch

markers may incorrectly be issued twice.

fails to replicate the update on a column of

varchar(max) datatype correctly.

moved the primary database's truncation point to

the end of the log, but the Mirror Replication

Agent internal locator is not updated.

the shadow table of a marked stored

procedure is incorrectly replicated.

transaction that contains both a marked stored

procedure execution and a row containing a LOB

column.

log is not under default location is

upgraded to a new version, Replication Agent

fails to start with error message "Error

while trying to register Initializing

Repository with the bean manager."

update part of attributes of a object type

print_errno' is sent to the Replication Server

while the Replication Server is also in the

middle of processing the command 'switch

active', the Replication Server may terminate

unexpectedly and generate a stack trace and a

core dump.

The previous version suggested user to create repository via ODBC.

Get PD12 repository,

On PD15 try to connect with repository

First message

-->"The repository cannot be upgraded using proxy"

Next message "The connection failed because the repository has not yet be installed..."

the 'stats_sampling' option turned on, the

Replication Server may terminate unexpectedly

and generate a stack trace and a core dump if a

replicated table name or replicated column name

approaches 255 characters in length.

Create a repository definition, do not associate a DMBS

Run Drop repository,

On connection dialog->Click 'OK'

-->Nothing happens

Workaround: manually resize window using mouse

customer's description:

Extract ("check out") multiple documents from repository: Minimize/Resize controls in upper right corner are missing. Just the "X" control is present. PD Version 12 provides the Minimize/Resize controls for similar functionality.

Customer's description:

When a repository object is 'locked' and comments are placed on the object to indicate the purpose of the lock, the comments are not viewable by anyone afterwards. We believe that these comments should be viewable, and should automatically be deleted when the object is 'unlocked'.

migrate from earlier versions of 15.0 to

lastest ESD with error "Device id (virtual page

number) and device name mismatch.

smallmoney can be incorrectly rounded during

replication.

be thrown when user invokes pdb_archive_remove

command before Replication Agent is

initialized.

always sends data in little endian order even

if ltl_big_endian_unitext is configured to true.

error occurs when Replication Agent scans

a log record that does not contain any

supplemental metadata.

processing a large message (i.e. a DML command

for a table with many columns), adding a new

partition may cause the Distributor thread or

the DSI thread to fail with ERROR #6025 ("Block

consistency failed ...").

disallows the creation of a partition on a raw

device if the specified partition size is

greater than 2GB.

sp_export_qpgroup can cause Mirror RepAgent

to go to ADMIN state. This issue is addresed

by upgrading to ASE 15.0

rasd_restore with a message similar to "Command

<rasd_backup> failed - The database backup

failed because: Could not create directory

<[directory]/repository/backup/previous_backup>."

recognize the entry 'LT=...' in SySAM properties

file.

replicate the last 10 characters of a

4,000 character column value.

Today, RepServer licensing is base on how big the machine is, the one where RS is running, but it does not mater how big (or how small) the application using RS is.

exception when it fails to connect to

Replication Server due to a syntax error

in the connection definition.

connection starts with a digit, or a non

standard character, such as "-", is present

in the data server name, Replication Agent

fails to connect to Replication Server.

to mark a second procedure with the same

name but a different owner, the error

message explaining the cause is not clear.

mark table/procedure with specified schema.

to ADMIN state when trying to add

a column with default value to a

marked table that contains data.

error message that indicates dropping of

auto created function replication definition

failed.

"SA password too long. Maximum length is 30 characters." in upgrade operation.

Values for money and smallmoney can be

incorrectly rounded when replicated.

publications, the Distributor thread may

deadlock with a DSI thread.

reproduce:

1.goto configuration and click notification

2.in the mail template, update the content of mail title

3.click save.it will show "Property value has not changed" message, in fact , it should have been update.

the same issue will occur for the continues update in the body content of the mail template.

off' the Replication Server will incorrectly

disable STS caching. This will result in an

increase in RSSD queries which in turn may

negatively impact Replication Server

performance.

change model comment and check-in again with "store prepared diagram"

diagram is not saved in repository

it should

index 'rs_key2_diskpartitions' for the RSSD

table 'rs_diskpartition' is incorrectly not

created.

'truncation_type' default is incorrectly set to

'interval'.

replication with error "IOException:

java.net.UnknownHostException" when the

primary database is unavailable.

replication environment is not configured to

allow DDL replication." is displayed if a

database level replication definition is not

configured in Replication Server.

replicating, an ArrayIndexOutOfBounds

exception occurs during cluster log scanner

positioning sending the Replication Agent

to ADMIN state.

in the ra_admin utility for upgrading Replication

Agent instances.

SYNTAX: ra_admin -u <upgrade_option>

PARAMETERS

-u <src_instance_dir>

Upgrade one instance of Replication Agent in

the specified source instance directory

to the product installation directory

-u <instance_name> | instance=<instance_name>

Upgrades only the specified instance of

Replication Agent in the current product

installation directory

-u all

Upgrade all instances of Replication Agent

within the current product installation

directory.

EXAMPLE:

To upgrade an individual instance in

a specified source instance directory to

the product installation directory.

ra_admin -u /opt/sybase/RAX-15_0/my_inst

To upgrade all the instances in the current

product installation.

ra_admin -u all

To upgrade a specific instance in the current

product installation directory.

ra_admin instance=my_inst

OR

ra_admin my_inst

NOTE:

- The -u <src_instance_dir> provides the

ability to upgrade an individal instance

from a previous major release to the

current release.

- The 'all' or '<inst_name>' or

'instance=<inst_name>' upgrade options

performs an upgrade of instance(s)

in the current product release. All

upgrades are performed directly on the

instance to be upgraded. The Replication

Agent instance configuration file is

backed before the upgrade for use in error

recovery, if required. If an error occurs,

the upgrade is rolled back. This option is

intended for performing upgrade of instances

between release to release in the same

major release such as a patch update.

Could not start the Sybase Unified Agent service on Local Computer.

Error 1067: The process terminated unexpectedly.

due to incorrect registy entry.

But these icon files have 256 colors, so many colors are lost.

And the background of icons have the "white" color instead of transparent color.

At that time, Customer is using "rs_subcmp" RepServer tools under Linux platform, but "rs_subcmp" abort when it rich the 4GB limit of used memory on large user table.

For this, Customer would like "rs_subcmp" be able to manage comparing on huge user table.

the 'pdb_setrepproc' command can return

an error: "Command <pdb_setrepproc>

failed - Could not list metadata for procedure

<procedure_name> because: Procedure

<procedure_name> is not in database

<database_name>."

with the <procName> return results containing dbo

qualifier in the replicate name column.

migrating from GA version to the latest ESD with

an error like "Reposition point <locator value>

is older than start of log point <second locator

value>."

when an invalid argument is specified

to the command "pdb_setrepproc".

column that contains NULL data, rs_subcmp will repeatedly generate

Open Client Library error 16843070.

Steps:

Take Server Configurations->General as example

1. Delete the value in "Session timeout"

2. Click Reset button

Result:

The value does not reset to the former one, still blank.

In Configurations page, all the reset button has the same behavior

prepare a pdm model with multiple version

Reproduce:

1.click at the model and go to permission

2.click expand all, there will popup a error page as follows:

java.lang.RuntimeException: Exception while invoking expression #{compareTree.expandTree}

at com.sybase.cmr.webrepository.webapp.filter.LocaleFilter.doFilterInternal(LocaleFilter.java:112)

at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:77)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)

at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)

at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)

at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)

at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)

at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)

at java.lang.Thread.run(Thread.java:595)

reproduce:

1.click a model and go to permission

2.delete the public group

3.add in user "a" with list permission

4.logout and login with user a

5.go to RE and and expand the tree, the postfix name of the model will list such as "examplel.pdm - v2";

To reproduce:

1>there are two head for exception page.

Attached the image.

fails to initialize when creating instance

from response file without setting

initialize_instance or start_instance

to true.

"Could not stop database <repository

database name>" error message.

shows an incorrect error message when an invalid

owner string is passed in.

to ADMIN state with an OutOfMemory error in

the log during ra_init if more than 1000

tables are in primary database.

process a rollback operation for off-row LOB

data.

reproduce:

1.go to search after login

2.click at a model in the tree

the repository path will show the model name and its model type as postfix,such as"/example.oom", but now the tree only show the model object "example", so there is no need to show the model type "oom" any more,same in the result table and general of object in the Repository Explore.

Steps:

1. Deactivate a user

2. In the user list, show the deactivate user

3. Click the checkbox before the user who is deleted in step1

Result:

The Deactivate button change to enable status

Steps:

1. Deactivate a user named "aa"

2. Select "Show deactivated members"

3. Select the checkbox before any user in the user list

4. Click "aa", change the status to "active"

5. Click Save button

Result:

After step5, page back to the user list, and the "Deactivate" button is still enabled

when the RMServices server attempts to delete rows from the rs_ticket_history the customer noticed the delete was taking a long time and blocking a maintuser <spid> that was attempting to do inserts ... so they used ... kill <spid> ... on the delete <spid> and then when they attempted in another client session with RMServices ... get heartbeat tickets from pds.pdb to rds.rdb ... they then get the following error...and also the rs_ticket_history table then begins to grow indefinitely large in rows from then on...

C:\ocs15e12\OCS-15_0\bin>isql -SRMServices -Usa -P -w2048

1> get heartbeat tickets from pds.pdb to rds.rdb

2> go

Msg 32000, Level 20, State 0:

Server 'RmaAgent', Procedure 'get heartbeat tickets from pds.pdb to rds.rdb', Line 1:

Failed to get heartbeat tickets.

1> quit

"java.lang.IndexOutOfBoundsException" error sends

Replication Agent to ADMIN state during

replication.

a table trunction is executed followed by a LOB

operation, Replication Agent encounters a LobObjectID

mismatch error.

remainder is too small' and 'BufferUnderflow-

Exception' occur randomly when Replica-

tion Agent is resumed.

When Customer create a subscription, he would reference the RepDef name as well as its source PDS/PDB info in its name for easy reference.

Because of the column length restriction, "subname" are usually heavily abbreviated to accommodate lengthy RepDef names (which would be from lengthy table names), which can be a real pain when trying to create unique subscription names for Customer.

So if Customer were to make use of the increased table(object) and RepDef name length, he would have even more difficulty abbreviating these into 30 character subscription names.

fails with an error "Could not list article

metadata because:

com.sybase.ds.mssql.entity.MSSqlSimpleArticle".

To reproduce:

1>For showing Deployment Instance object in EAM, if it is deployed by "application_1" with no instance name, it will be shown in " " in CMR, and show "Deployment Instance" for all objects.

It should be deal with specially for the special object.

Attached the EAM.

value of configuration parameter

pds_interfaces_file.

monitor Oracle online and archive log device read

status.

Online log statistics:

1.Average time (ms) per online log device read

2.Total online log read time (ms)

3.Current blocks per device read(online log)

Archive log statistics:

1.Average time (ms) per archive log device read

2.Total archive log read time (ms)

3.Current blocks per device read(archive log)

command with the 'all, enable' option is not

supported and should return an error message.

for materialized view are incorrectly marked

during initialization with pdb_automark_tables

property setting to true.

This is an issue from UNIBANCO toptier customer.

When two users are dealing with same RQM model extracting/changing/consolidating repository, the merge of changes are not bringing all subitems as expected. Also, in PD 12.5 only, some subitem descriptions get changed.

index that duplicates another data column during

operation processing stops replication.

by a "rasd_backup" operation.

results in replicate database constraint

violation.

To reproduce:

If repository db is SQL Server 2000, the installer can't connect it successfully.

And can't show data in web browser.

We need to support SQL Server 2000.

functionality in the sybfilter driver. When an

error occurs, the error is logged to an

error file (sybfilter.err). When the trace flag

is enabled, the trace information will be logged

to a trace file(sybfilter.trc). These two files

will reside in the same directory where the

configuration file is located.

There are four level of trace info which can be

configured by users in sybfiltermgr. The default

setting is to output the error message only.

trace

Turn on or off sybfilter trace

Syntax

trace [T1] [T2] [T3] [T4] [all] [off]

Default

T4 - Log error messages

Parameters

T1 Logs driver routine entrance and

return messages

T2 Logs operation status information

T3 Logs normal message such as an

exclusive open file operations

T4 Log error messages

all Logs T1, T2, T3 and T4 level messages

off Turns off tracing

Example:

To turn on T3 trace:

trace T3

To turn on T1 and T3 trace:

trace T1 T3

To turn off trace

trace off

To display help on trace command:

help trace

Server with "error ORA-00900: invalid SQL

statement" due to an attempt to replicate only

the second half of a DDL command.

description from 'Average number of checkpoints

per records read' to be 'Average number of log

records per checkpoint'.

Rep Agent dies with 'Invalid block id'

when log scanner tries to position.

and then re-initialization do not refresh the user articles

information stored in the Replication Agent System Database

repository.

IBMPLINUX64 RS 1510 GA incorrectly

allows the user to optionally configure

the Replication Server with an embedded

RSSD (ERSSD). The 'rs_init' executable

should disallow this option since an

ERSSD requires SQL Anywhere and SQL

Anywhere is not available on

IBMPLINUX64.

generate a replication definition

after re-setting the pdb_auto_create_repdefs

configuration property to 'true'.

duplicate count increases and the replicate

connection DSI goes down with error 5147 because

parallel transactions with affected LOBs result

in the wrong locator getting sent by Replication

Agent for some operations.

is 'sa', Replication Agent goes into ADMIN state

with UserNotFoundException error.

the parameter name in the stored prcoedure

contains Oracle reserved words.

Expanding documents in Repository browser leads to java.lang.RuntimeException.

create cluster table DDL operation.

integrate only happen in the last version of a branch. As well it shouldn't be possble to unfreeze any version except the last one of a branch in the GUI

command will fail with error message "The database

transaction log file move failed because: Could

not move file <src_file_location> to

<target_file_location>".

When the repository update script is executed outside of PowerDesigner, you unable to connect to the repository with existing users. When attempting to connect, you get the following error message:

Invalid repository user or password!

If you execute the update script within PowerDesigner, then you are able to connect to the repository.

shows an incorrect error message when

an invalid owner string is passed in.

replication that executes with error returns

corrupt error stack.

replication and the stored procedure contains a

truncate table command, both the truncate

command and stored procedure execution are

replicated.

for replication fails at the primary database,

no message is logged indicating the procedure

will still be executed at the replicate database.

a stored procedure that is not marked for

replication is ignored by Replication Agent.

procedure that has an OUTPUT parameter results in

an error in the Replication Server DSI thread

similar to: PLS-00306: wrong number or types of

arguments in call to 'MY_PROC'.

To reproduce:

1) create and save any model (test.pdm)

2) create a folder in the repository (folder_1)

3) right-click on folder_1 and select Add

4) browse to and select test.pdm

5) click open

Note: You are prompted with dialog asking if you want to use the model in the current workspace.

6) Click NO to the dialog

NOTE: Test.pdm will be checked-in under folder_1

7) cancel

repeat steps 3, 4, 5 but this time click YES to the dialog

NOTE: Test.pdm will be checked-in under the root of the repository.

This behavior exists in v9.5, 10.1.0, 11.1.0, 12.5., and 15.0

when pds_interfaces_file is set to

<not_configured> in the instance

configuration file.

string is invalid." error message.

for a table if the table is created before

executing 'ra_init'.

view are incorrectly replicated.

OS: Windows 2003 SP2

This is an issue from UNIBANCO customer.

After extrating a model from repository, picture that was inserted via "import image" is not displayed inside model. Only picture's area is displayed. If customer uses copy/paste when inserting pictures, then issue doesn't occur.

or earlier, and communicating with Replication

Server release 15.2 or later, the Replication

Agent query against the Replication Server System

Database to obtain replication definition

information fails to return the appropriate rows.

This failure causes the Replication Agent to fail

with a 'replication definition not found' error.

unmarked and re-marked during migration.

Failure of re-marking stored procedures will

be logged as error in Replication Agent error

log, and ra_migrate just return success.

Customers must review the error log and may be

required to do manual re-marking.

A list of procedures which need to be manually

re-marked will be provided in the error log.

Two limitations during migration:

1. Marked stored procedures that are executed in

the primary database during migration will not be

replicated.

2. DDL operations done in primary database

between last truncation point and the end of

migration will not be replicated because DDL

replication will be disabled internally by

Replication Agent during migration.

execution of procedure if procedure is altered

to add a new parameter.

This cause him awful performance when calling "rs_helprep".

Looking at "rs_helprep" RS system store proc source code, it create and populate a temporary table before processing user request.

Steps to create and populate this temporary table are:

1- create the temporary table

2- populate the temporary table using "insert ... select ..." statement

3- update data in temporary table, one row by one row.

Third steps is the one that may cause poor performance (due to SQL code doing a loop and simulating what could be done using cursors).

The INSERT statement into temporary table "#rs_repinfo" could be improved in order to avoid doing step 3.

Suggesting change:

Original RS 15.1 "INSERT" statement:

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

/* Initialize #rs_repinfo from rs_databases, rs_objects, rs_sites */

insert into #rs_repinfo (objid, objname, prs, prds, prdb, phys_tablename,

phys_objowner, deliver_as_name, repl_objowner, crdate, dbid)

select ro.objid, ro.objname, rs.name, rd.dsname, rd.dbname,

ro.phys_tablename, ro.phys_objowner, ro.deliver_as_name,

ro.repl_objowner, ro.crdate, rd.dbid

from rs_objects ro, rs_sites rs, rs_databases rd

where ro.prsid = rs.id and

rd.dbid = ro.dbid and

ro.objname not like "rs_in%" and

ro.objname not like "rs_drp%"

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

Could be updated as following:

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

/* Initialize #rs_repinfo from rs_databases, rs_objects, rs_sites */

insert into #rs_repinfo (objid, objname, prs, prds, prdb, phys_tablename,

phys_objowner, deliver_as_name, repl_objowner, crdate, dbid,

/* adding following column */

type, phys_owner_tab, repl_owner_tab)

select ro.objid, ro.objname, rs.name, rd.dsname, rd.dbname,

ro.phys_tablename, ro.phys_objowner, ro.deliver_as_name,

ro.repl_objowner, ro.crdate, rd.dbid,

/* adding following value to populate all columns at same time */

case ro.objtype

when 'R' then 'Tbl'

when 'F' then 'Func'

else 'Sys'

end,

case ro.phys_objowner

when ' ' then ro.phys_tablename

else substring (ro.phys_objowner + '.' + ro.phys_tablename, 1, 255)

end,

case ro.repl_objowner

when ' ' then ro.deliver_as_name

else substring (ro.repl_objowner + '.' + ro.deliver_as_name, 1, 255)

end

from rs_objects ro, rs_sites rs, rs_databases rd

where ro.prsid = rs.id and

rd.dbid = ro.dbid and

ro.objname not like "rs_in%" and

ro.objname not like "rs_drp%" and

/* adding following where clause to select, at the source, only wanted RepDef */

ro.objname like isnull (@object, '%') + '%'

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

So next block statement could be removed:

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

/* remove following block statement, not needed any more due to above change in population #rs_repinfo table */

/*

select @cur_rep = min(objid) from #rs_repinfo

while @cur_rep != NULL

begin

-- get the type from rs_objects

select @temp = objtype,

@powner = phys_objowner, @ptable = phys_tablename,

@rowner = repl_objowner, @rtable = deliver_as_name

from rs_objects

where objid = @cur_rep

if (@temp = 'R')

select @type = "Tbl"

else if (@temp = 'F')

select @type = "Func"

if (@powner != " ")

select @ptable = substring(@powner+'.'+@ptable, 1, 255)

if (@rowner != " ")

select @rtable = substring(@rowner+'.'+@rtable, 1, 255)

update #rs_repinfo

set type = @type,

phys_owner_tab = @ptable,

repl_owner_tab = @rtable

where objid = @cur_rep

-- get the next entry

select @cur_rep = min(objid)

from #rs_repinfo

where objid > @cur_rep

end

*/

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

This performance improvement request is also valid for RS 12.6 / RS 15.0x

with error "OracleRuntimeException:

Off-row LOB leaf update contains unexpected

values".

Agent is running on HP Itanium and connecting to

a UDB server on a platform that has a different

endian architecture.

If RepServer is shut down, following error are reported on the console (session where RepServer is started):

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

F. 2008/12/31 02:11:39. FATAL ERROR #1023 USER(sa) - r/errlog.c(309)

Received error 'File too large' while writing 'Shutting down.' to the error log.

E. 2008/12/31 02:11:39. ERROR #1033 USER(sa) - r/errlog.c(419)

Unable to log an error.

F. 2008/12/31 02:11:39. FATAL ERROR #1033 USER(sa) - r/errout.c(564)

Unable to log an error.

I. 2008/12/31 02:11:39. Shutting down.

F. 2008/12/31 02:11:39. FATAL ERROR #1033 USER(sa) - r/errout.c(564)

Unable to log an error.

F. 2008/12/31 02:11:39. FATAL ERROR #1023 USER(sa) - r/errlog.c(309)

Received error 'File too large' while writing '

T. 2008/12/31 02:11:39. (17): ' to the error log.

T. 2008/12/31 02:11:39. (17): F. 2008/12/31 02:11:39. FATAL ERROR #1023 USER(sa) - r/errlog.c(309)

Received error 'File too large' while writing 'Exiting due to a fatal error' to the error log.

Exiting due to a fatal error

F. 2008/12/31 02:11:39. FATAL ERROR #1023 USER(sa) - r/errlog.c(309)

Received error 'File too large' while writing '' to the error log.

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

RepServer also fail to start when its errorlog size is greater than 2GB:

- console output:

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

F. 2008/12/31 01:22:50. FATAL ERROR #1024 GLOBAL RS(GLOBAL RS) - r/errlog.c(114)

Failed to open log file '/remote/cases/11497000s/11497724/RS126_SUNBEAM.log' due to file error 'Value too large for defined data type'.

F. 2008/12/31 01:22:50. FATAL ERROR #1025 GLOBAL RS(GLOBAL RS) - r/errapp.c(376)

Logging failed because the log is not open.

F. 2008/12/31 01:22:50. FATAL ERROR #18028 GLOBAL RS(GLOBAL RS) - servmain.c(334)

Initialization failed. Server is shutting down.

F. 2008/12/31 01:22:50. FATAL ERROR #1033 GLOBAL RS(GLOBAL RS) - r/errout.c(564)

Unable to log an error.

F. 2008/12/31 01:22:50. FATAL ERROR #18028 GLOBAL RS(GLOBAL RS) - servmain.c(291)

Initialization failed. Server is shutting down.

F. 2008/12/31 01:22:50. FATAL ERROR #1033 GLOBAL RS(GLOBAL RS) - r/errout.c(564)

Unable to log an error.

T. 2008/12/31 01:22:50. (-1): Exiting due to a fatal error

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

This works fine using RepServer 15.x (tested on RS 15.0.1)

ASM for storage management can result in multiple

database entries in ASM causing the Replication

Agent to go to ADMIN state with the error: "More

than one row returned for ASMAlias for database

name".

a materialized view is not filtered

out correctly by Replication Agent

when all tables are marked for

replication.

RACFGFilePath as a user variable instead of a

system variable, Sybfilter manager will throw an

error "could not connect to filter: 0x80070002".

rep1510:

< drwxr-xr-x 15 ylacramp sybase 512 Jan 16 11:43 REP-15_1

---

> drwx------ 15 ylacramp sybase 512 Jan 16 11:43 REP-15_1

rep1510/REP-15_1:

< drwxr-xr-x 2 ylacramp sybase 512 Jan 16 11:42 bin

< drwxr-xr-x 2 ylacramp sybase 512 Jan 16 11:42 doc

< drwxr-xr-x 3 ylacramp sybase 512 Jan 16 11:42 install

< drwxr-xr-x 3 ylacramp sybase 512 Jan 16 11:43 locales

< drwxr-xr-x 2 ylacramp sybase 2560 Jan 16 11:42 scripts

< drwxr-xr-x 2 ylacramp sybase 512 Jan 16 11:42 upgrade

---

> drwx------ 2 ylacramp sybase 512 Jan 16 11:42 bin

> drwx------ 2 ylacramp sybase 512 Jan 16 11:42 doc

> drwx------ 3 ylacramp sybase 512 Jan 16 11:42 install

> drwx------ 3 ylacramp sybase 512 Jan 16 11:43 locales

> drwx------ 2 ylacramp sybase 2560 Jan 16 11:42 scripts

> drwx------ 2 ylacramp sybase 512 Jan 16 11:42 upgrade

rep1510/REP-15_1/bin:

< -rwxr-xr-x 1 ylacramp sybase 13173912 Apr 17 2008 repserver

< -rwxr-xr-x 1 ylacramp sybase 67930536 Apr 17 2008 repserver.diag

< -rwxr-xr-x 1 ylacramp sybase 4828292 Apr 17 2008 rs_subcmp

---

> -r-xr-x--- 1 ylacramp sybase 13422692 Nov 12 21:30 repserver

> -r-xr-x--- 1 ylacramp sybase 68726944 Nov 12 21:25 repserver.diag

> -r-xr-x--- 1 ylacramp sybase 4829836 Nov 12 21:31 rs_subcmp

rep1510/REP-15_1/doc:

< -rw-r--r-- 1 ylacramp sybase 471079 Apr 17 2008 error_messages_rs

< -rw-r--r-- 1 ylacramp sybase 53861 Apr 17 2008 error_messages_subcmp

---

> -r--r----- 1 ylacramp sybase 487874 Nov 12 21:14 error_messages_rs

> -r--r----- 1 ylacramp sybase 53861 Nov 12 21:17 error_messages_subcmp

rep1510/REP-15_1/install:

< -rwxr-xr-x 1 ylacramp sybase 5908448 Apr 30 2008 rs_init

---

> -r-xr-x--- 1 ylacramp sybase 5912056 Nov 12 21:59 rs_init

rep1510/REP-15_1/locales:

< drwxr-x--- 3 ylacramp sybase 512 Jan 16 11:43 us_english

---

> drwx------ 3 ylacramp sybase 512 Jan 16 11:43 us_english

rep1510/REP-15_1/locales/us_english:

< drwxr-x--- 3 ylacramp sybase 512 Jan 16 11:43 utf8

---

> drwx------ 3 ylacramp sybase 512 Jan 16 11:43 utf8

rep1510/REP-15_1/locales/us_english/utf8:

< -rw-r----- 1 ylacramp sybase 270114 Mar 27 2008 rs.loc

---

> -r--r----- 1 ylacramp sybase 279205 Nov 12 20:43 rs.loc

rep1510/REP-15_1/scripts:

< -rw-r--r-- 1 ylacramp sybase 4248 Aug 25 2003 hds_clt_ase_to_db2.sql

< -rw-r--r-- 1 ylacramp sybase 3396 Aug 25 2003 hds_clt_ase_to_udb.sql

< -rw-r--r-- 1 ylacramp sybase 10758 Feb 27 2008 hds_db2_udds.sql

< -rw-r--r-- 1 ylacramp sybase 36517 Feb 27 2008 hds_oracle_udds.sql

< -rw-r--r-- 1 ylacramp sybase 12689 Feb 27 2008 hds_udb_udds.sql

< -rw-r--r-- 1 ylacramp sybase 512445 Apr 3 2008 rs_install_systables_asa.sql

< -rw-r--r-- 1 ylacramp sybase 511832 Apr 3 2008 rs_install_systables_ase.sql

---

> -r--r----- 1 ylacramp sybase 4924 Sep 23 07:43 hds_clt_ase_to_db2.sql

> -r--r----- 1 ylacramp sybase 4540 Sep 23 07:43 hds_clt_ase_to_udb.sql

> -r--r----- 1 ylacramp sybase 13714 Sep 23 07:49 hds_db2_udds.sql

> -r--r----- 1 ylacramp sybase 36518 Oct 13 06:41 hds_oracle_udds.sql

> -r--r----- 1 ylacramp sybase 15631 Sep 23 08:01 hds_udb_udds.sql

> -r-xr-x--- 1 ylacramp sybase 515226 Oct 23 01:35 rs_install_systables_asa.sql

> -r-xr-x--- 1 ylacramp sybase 514613 Oct 23 01:35 rs_install_systables_ase.sql

rep1510/REP-15_1/upgrade:

< -rw-r--r-- 1 ylacramp sybase 290206 Apr 4 2008 rsupgr_asa.sql

< -rw-r--r-- 1 ylacramp sybase 293453 Apr 4 2008 rsupgr_ase.sql

---

> -r-xr-x--- 1 ylacramp sybase 305894 Oct 23 01:35 rsupgr_asa.sql

> -r-xr-x--- 1 ylacramp sybase 309141 Oct 23 01:35 rsupgr_ase.sql

The List of Locks window displays the older name of the project under Name column but Location is correct.

No problem when renaming a folder.

replicated correctly to the target database when

the lr_ntext_byte_order configuration parameter

is set to 'little' and the ltl_big_endian_unitext

configuration parameter is set to 'false'.

Update value of udd to null, RepAgent

will sent value as 0.

Customer site has migrated from PD v12.5 to 15. For the repository they use SQL Server 2005 and the use 'windows authentication' for all logins. They will have 300+ users accessing CMR.

After installing CMR, I modify the connectionURL in the \config\repository.xml file and enter

jdbc:sqlserver://<servername>:1433;databaseName=<dbname>;integratedSecurity=true;

this is the same connection URL from a working connection profile in PowerDesigner.

When I restart the tomcat server and attempt to connect to the repository, the connection fails. In the cmrserver.log file, the following message is logged:

FATAL Thread-1 2009/01/22 17:54:09 EST com.sybase.cmr.infra.server.persistence.db.connection.DBCPConnectionProvider.init(DBCPConnectionProvider.java:194) Cannot create PoolableConnectionFactory (This driver is not configured for integrated authentication.)

FATAL Thread-1 2009/01/22 17:54:09 EST com.sybase.cmr.infra.server.persistence.db.connection.DBCPConnectionProvider.init(DBCPConnectionProvider.java:195) Failed to initialize database connection.

Also, notice that the accelerator on the menu is 'CTRL+ALT+O but in the Browser it is CTRL+ALT+E

To reproduce:

1) connect to a PD 15 repository

2) select 'check out' from the repository menu

Note: the Check out window does not launch

created under certain conditions will not be

fully replicated, which will cause the

Replication Agent to stop replicating.

with a base type of varchar is incorrectly

treated as type 'longsysname'.

error "TransactionException: Can not find

relative operation locator of CLR".

1) create logical connection with the same or diff name as ds.db for active connection

2) create table repdef with or without send standby all columns or

msa(multiple site availability)db repdef

using logical connection

3) add active connection to logical connection

4) attempt to drop active connection

state when processing a truncate table DDL

operation.

rasd_backup_dir, rasd_database,

rasd_trace_log_dir, rasd_tran_log, and

rasd_tran_log_mirror are incorrect.

property now provides the option to include the

Oracle unique database name with the ASM disk

group name in order to identify the location in

ASM that archived log files are stored.

pdb_archive_path

This parameter is available only for Oracle and

UDB.

Identifies the directory path where the

Replication Agent expects to find archived redo

log files (for Oracle) or archived transaction

log files (for UDB). When archived redo log files

or archived transaction log files are stored in

the file system, the configuration parameter is

set to a file system path.

Default

<not configured>

Values

For Oracle, a valid directory path on the machine

hosting the Replication Agent that points to a

location where Oracle places the archived redo

log files. For example,

ORACLE_HOME\oradata\orcl\archive

For Oracle, when archived redo log files are

stored in Oracle ASM, the configuration parameter

must be set to the name of the ASM disk group

where the archived redo log files are stored.

The disk group name must be preceded with a plus

�+� sign to specify the archive redo log path as

an ASM disk group. For example,

+dgroup_01

For Oracle, when archived redo log files are

stored in Oracle ASM and the Oracle datbase

name and unique database name are different, the

configuration parameter must be set to the name

of the ASM disk group and database name where the

archived redo log files are stored. The disk

group name must be preceded with a plus �+� sign

to specify the archive redo log path as an ASM

disk group followed by a path separator "/" and

database name. For example,

+dgroup_01/XDMQALDA

For UDB, a valid directory path on disk, as

defined by the UDB LOGARCHMETH1 or LOGARCHMETH2

database configuration parameter, when it is

configured to DISK. For example,

<path>

Comments

Setting of the configuration parameter is

required when configuration property

pdb_include_archives is set to true, and must be

set to a valid location before the Replication

Agent can be placed in a replicating state.

If the Replication Agent cannot find an expected

log record in the Oracle online redo logs, the

Replication Agent will search this directory for

the archived log file containing the required

record.

For UDB, pdb_archive_path must be configured

before pdb_archive_remove is enabled

(set to true).When pdb_archive_remove property is

set to true, Replication Agent for UDB truncates

the archived log files from the location

specified by pdb_archive_path.

See also pdb_archive_remove and

pdb_include_archives.

with 'rs_zeroltm', the Replicatin Agent expects to

receive a zero value from the Replication Server with the 'get

truncation' command. Due to uninitialized

values, a non-zero value is incorrectly received

instead.

Replication Agent would automatically create

replication definitions during ra_init

processing, if configuration property

pdb_auto_create_repdefs is set to true. Now,

in order to shorten the length of time

required for ra_init processing, automatic

creation of replication definitions in

Replication Agent for Oracle has been removed

from ra_init processing, regardless of the

setting of pdb_auto_create_repdefs.

Customers who wish to have replication

definitions created for all tables marked during

execution of ra_init, should execute command

rs_create_repdefs with the 'all' keyword after

ra_init execution.

Wed Feb 11 09:00:17 2009 LTMAPI: LTMPACKR return rc= 432160972.

Regression, the line to set the return code when building or checking a Compensation Log Record (CLR) was missing.

a BufferUnderFlowException when updating a LOB

column in a table from a null value to a non-null

value.

replication definition for a table containing a

clob datatype as a text datatype for three bytes

character set.

the execution of stored procedure which have 4

char parameters.

NullPointerException when processing a create/drop

materialized view statement.

agent instance fails with a NullPointerException.

migration with an error similar to "Session

repository has multiple entries for session with

instance id <1>, sid <88> and version

<0x000000000d073ef20001000100000b6a0000020d00900

0000000000000000000>".

does not unmark all tables.

when executed after "pdb_setrepproc all, disable".

a replication definition for a table containing

a FLOAT column.

The Check In has detected that the local document and the repository document are identical. The check in has been canceled.

fails.

pdb_dac_port_number configuration property is set

to an incorrect value, Replication Agent

fails to initialize with a mis-leading error

message "The server is not started in single user

mode".

an error, instead of returning 0 rows, when the

command is executed for a table that does not

exist.

system procedure call, sp_setrepproc, can not be

replicated correctly when Replication Agent

unmarks a procedure in the primary site.

RepAgent throws NullPointerException

when replicating sp_rename.

SET WALLET OPEN' will cause Replication Server

DSI connection to suspend.

'truncation_type' is incorrectly set to 'INTERVAL'

instead of 'LOCATOR_UPDATE'.

defined as 'DEDUPLICATE' may cause Replication

Agent to go to ADMIN state.

with a NullPointerException when trying to alter

a table to modify lob columns.

error similar to "Error initializing change

vector <###> in log record <###> because: null".

'STS, STS_DONT_CACHE' is enabled.

DDL command is not replicated to the

replicate site, which was issued just

before "pdb_setrepddl disable" command.

In List of Users window, Find a row tool currently opens to search an item in the list based on displayed columns.

a replication definition for multi-byte LOB

column as text datatype.

the maintanance user are not filtered out for replication.

procedure which has no blank or '/n' between the

procedure specification and the final return.

RepAgent 12.5, trigger based release, for Oracle, the store procedure "RA_BLD_REPTRAN_" does not report exception that had occured from RAO system table "RA_EXCEPTION_" when the SQL_Code is negatif (less than 0).

When RepAgent scan the shadow log, it call store proc "RA_BLD_REPTRAN_", this store proc may raise an execption (error 20.000) when exception have been logged in the exception system table "RA_EXCEPTION_" :

RA_BLD_REPTRAN_ source code:

/** check for exceptions, raise -20000 error if any have been registered **/

SELECT COUNT(*) INTO NUM_TRANS FROM RA_EXCEPTION_ WHERE sql_code_ > 0;

IF ( NUM_TRANS > 0 ) THEN

RAISE_APPLICATION_ERROR ( -20000, 'RAO exceptions have been logged');

END IF;

In this peace of code, the WHERE clause "sql_code_ > 0" does not include all exceptions where error code is negatif.

This cause RepAgent to be restarted even the "RA_EXCEPTION_" system table is not cleared, and cause next exception to not be logged.

This code could be change like this: ("sql_code_ <> 0")

/** check for exceptions, raise -20000 error if any have been registered **/

SELECT COUNT(*) INTO NUM_TRANS FROM RA_EXCEPTION_ WHERE sql_code_ <> 0;

IF ( NUM_TRANS > 0 ) THEN

RAISE_APPLICATION_ERROR ( -20000, 'RAO exceptions have been logged');

END IF;

Doing this, the RepAgent exception table will need not allow RepAgent to restart before exception table is cleaned and so next exception will not be lost.

value('') for image data type is replicated as

non-empty data to the replicate site.

Replication Agent goes into ADMIN state

when replicating table with LOB columns.

replicate a rollback operation on an off-row LOB

column.

error "Procedure 'pdb_truncate_xlog',

Line 1: Illegal command: <pdb_truncate_xlog>".

EndOfLogException during RBA search positioning

sends the Replication Agent back to ADMIN state.

Off-row LOB leaf update contains unexpected

values" causes the Replication Agent to suspend

replication.

select origin, origin_qid, secondary_qid from rs_lastcommit

E. ... ERROR #5094 DSI(104 oracle_dco.oracle_dco) - /dsioqid.c(1781)

The second and third columns returned by the rs_get_lastcommit function should

have type 'binary' or 'char'. The one returned from database 'oracle_dco.

oracle_dco' for column 2 is not 'binary' or 'char'. It is '2' as defined by CS_LIB.

I. ... The DSI thread for database 'oracle_dco.oracle_dco' is shutdown.

REHL5.2 (2.6.18-92.el5) x86_64

we need to change the syntax for creating the rs_lastcommit table in

hds_oracle_setup_for_replicate.sql

should be...

create table rs_lastcommit

(

origin number(8),

origin_qid char(72 byte),

secondary_qid char(72 byte),

origin_time date,

dest_commit_time date

)

go

When accessing a repository created in SQL Server 2005 via CMR, the following error appear in CMR logs right after starting up CMR service:

ERROR Thread-1 2009/03/12 10:29:34 BRT com.sybase.cmr.infra.server.persistence.db.metacommands.LoadMetaModelCmd.execute(LoadMetaModelCmd.java:144) Unrecoverable exception occurred during loading of metamodels from repository

java.lang.NullPointerException

at java.util.Hashtable.get(Hashtable.java:336)

at com.sybase.cmr.infra.server.persistence.db.ExtendedMetaData.getMetaPackageExtendedMetaData(ExtendedMetaData.java:129)

at com.sybase.cmr.infra.server.persistence.db.DbMetaPersistenceManagerImpl.createMetaPackages(DbMetaPersistenceManagerImpl.java:589)

at com.sybase.cmr.infra.server.persistence.db.metacommands.LoadMetaModelCmd.execute(LoadMetaModelCmd.java:106)

at com.sybase.cmr.infra.server.persistence.db.command.CommandWrapper.execute(CommandWrapper.java:107)

at com.sybase.cmr.infra.server.persistence.db.command.TxCommand.execute(TxCommand.java:83)

at com.sybase.cmr.infra.server.persistence.db.command.CommandStackImpl.execute(CommandStackImpl.java:58)

at com.sybase.cmr.infra.server.persistence.db.DbMetaPersistenceManagerImpl.loadAllMetaModels(DbMetaPersistenceManagerImpl.java:342)

at com.sybase.cmr.infra.server.persistence.db.DbMetaPersistenceManagerImpl.loadAllMetaModels(DbMetaPersistenceManagerImpl.java:112)

at com.sybase.cmr.infra.server.meta.management.MetaModelManagerImpl.loadMetaModels(MetaModelManagerImpl.java:227)

at com.sybase.cmr.infra.server.impl.RepositoryImpl.init(RepositoryImpl.java:753)

at com.sybase.cmr.infra.server.impl.RepositoryImpl.<init>(RepositoryImpl.java:203)

at com.sybase.cmr.infra.server.impl.RepositoryImpl.<clinit>(RepositoryImpl.java:112)

at com.sybase.cmr.infra.server.RepositoryFactory.createRepository(RepositoryFactory.java:27)

at com.sybase.cmr.webrepository.webapp.servlet.CMRHttpServlet.init(CMRHttpServlet.java:62)

at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1139)

at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:966)

at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3956)

at org.apache.catalina.core.StandardContext.start(StandardContext.java:4230)

at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)

at org.apache.catalina.core.StandardHost.start(StandardHost.java:736)

at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)

at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)

at org.apache.catalina.core.StandardService.start(StandardService.java:448)

at org.apache.catalina.core.StandardServer.start(StandardServer.java:700)

at org.apache.catalina.startup.Catalina.start(Catalina.java:552)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)

at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)

at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)

If the repository is not empty, the following error also occurs when trying to expand Default Treeview within Repository Explorer Tab:

ERROR http-3030-Processor25 2009/03/12 10:30:29 BRT org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260) Servlet.service() for servlet Blocking Servlet threw exception

java.lang.RuntimeException: Could not find metaclass with the specified id 1106.

at com.sybase.cmr.webrepository.webapp.filter.LocaleFilter.doFilterInternal(LocaleFilter.java:112)

at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:77)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)

at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)

at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)

at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)

at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)

at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)

at java.lang.Thread.run(Thread.java:595)

generated in sequential order if the log file to

be backed up is exclusively locked by other

application.

command has been enhanced to accept

two kinds of schedule string. The current support

restricted UNIX cron style format and now a full

UNIX cron style format to support range and step

schedule.

The following is a valid schedule string in the

full UNIX cron style format:

[mm] [HH] [DOM] [MON] [DOW]

Note:

- Similar to the restricted UNIX cron style

schedule, a full UNIX cron style have

5 fields: mm, HH, DOM, MON and DOW,

The schedule format consists of 5

fields:

- minutes

- hours

- day of month

- month

- day of week.

- Each of the fields must be separated

by a whitespace. The schedule string

must be enclosed in double quotation marks.

- A list of values, a range of values or

a range of stepped values can be specified

in each fields so that a series schedule

can be specified in one command.

- List values in form i,j,k, which means

integer values applying to a field are i,j

and k. For example, schedule

"1,2,8,10 20 * * *" represents 8:01 pm,

8:02 pm, 8:08 pm, 8:10 pm every days.

- Range values in form of i-j, which means any

integer value from i to j. For example,

0-59 represents values 0,1,2,3,4,5,...58,59;

schedule "0-59 20 * * * " represents every

minutes in 8 pm.

- Step values in form of i-j/n, which means

any value from i to j stepped by n. For

example, 1-10/4 represents values 1,5,9.;

schedule "1-10/4 20 * * *" represents

8:01pm, 8:05 pm and 8:09 pm.

performing migration causes Mirror Replication

Agent to fail with NullPointerException.

still marked after Mirror Replication Agent

is re-initialized.

ma_admin) with the " -u <instance_dir>" option

is unable to upgrade the instance if the specified

source instance directory is a relative path with

no file separator.

@"DS_DOMICILIO"='Calle Baltasar D'Espanya 00002

Bajo',

Custom function strings with a quoted constant in the select cannot be used with quoted identifiers and subscription materialization.

The display in the repository explorer is now confusing: new name is displayed in local browser, old name is displayed in repository browser.

message like "No entry found in oracleLob with

the LOB Column <BLOB_COL> in table <RAUSER>.<TAB>"

is thrown when checking whether the object is in

encrypted tablespace or not.

supported Oracle version with message "version

... is not supported" after Replication Agent

attempts to initialize against an unsupported

Oracle version.

defined in encrypted tablespace is successful

when it should not be allowed.

sends the Replication Agent to ADMIN state.

property now provides the option to include the

Oracle unique database name with the ASM disk

group name in order to identify the location in

ASM that archived log files are stored.

pdb_archive_path

This parameter is available only for Oracle.

Identifies the directory path where the

Replication Agent expects to find archived redo

log files (for Oracle). When archived redo log files

or archived transaction log files are stored in

the file system, the configuration parameter is

set to a file system path.

Default

<not configured>

Values

For Oracle, a valid directory path on the machine

hosting the Replication Agent that points to a

location where Oracle places the archived redo

log files. For example,

ORACLE_HOME\oradata\orcl\archive

For Oracle, when archived redo log files are

stored in Oracle ASM, the configuration parameter

must be set to the name of the ASM disk group

where the archived redo log files are stored.

The disk group name must be preceded with a plus

�+� sign to specify the archive redo log path as

an ASM disk group. For example,

+dgroup_01

For Oracle, when archived redo log files are

stored in Oracle ASM and the Oracle database

name and unique database name are different, the

configuration parameter must be set to the name

of the ASM disk group and database name where the

archived redo log files are stored. The disk

group name must be preceded with a plus �+� sign

to specify the archive redo log path as an ASM

disk group followed by a path separator "/" and

database name. For example,

+dgroup_01/XDMQALDA

Comments

Setting of the configuration parameter is

required when configuration property

pdb_include_archives is set to true, and must be

set to a valid location before the Replication

Agent can be placed in a replicating state.

If the Replication Agent cannot find an expected

log record in the Oracle online redo logs, the

Replication Agent will search this directory for

the archived log file containing the required

record.

See also pdb_archive_remove and

pdb_include_archives.

may take a long time to complete.

data in LTL is not consistent with the value for

lr_ntext_byte_order setting.

transaction on a multi-block undo enabled Oracle

database.

If the associated Rep Server was authenticated first, you may get the following exception in the SCC (UAF) console when you authenticate an ASEMAP ASE:

[ASEMAP:][ERROR] [btpool1-3] Exception invoking method getRelatedManagedObjects javax.management.RuntimeOperationsException: Exception invoking method getRelatedManagedObjects.

If you continue and schedule collections for all servers, the collection jobs appear to run successfully - no errors are thrown as the collections are running. When you launch the ASE Monitor for the ASEMAP ASE you may get a pop-up error:

  The ASEMO does not contain all the child MO(s).

燙lick OK, and the ASE Monitor displays, but no data will be displayed on the Rep Agent screen

When multiple routes are created concurrently, deadlock might happen.

15.1 GA and communicating with Replication

Server 15.2 or later, the Mirror Replication Agent

query against the Replication Server System

Database to obtain replication definition

information fails to return the appropriate rows.

This failure causes the Mirror Replication Agent

to fail with a 'replication definition not found'

error.

fail to locate the Oracle timezone file even

though the ORACLE_HOME environment setting is

defined correctly.

instance can not start up after upgrading from

pre-15.1 to current release version.

in the ra_admin utility for upgrading Replication

Agent instances.

SYNTAX: ma_admin -u <upgrade_option>

PARAMETERS

-u <src_instance_dir>

Upgrade one instance of Replication Agent in

the specified source instance directory

to the product installation directory

-u <instance_name> | instance=<instance_name>

Upgrades only the specified instance of

Replication Agent in the current product

installation directory

-u all

Upgrade all instances of Replication Agent

within the current product installation

directory.

EXAMPLE:

To upgrade an individual instance in

a specified source instance directory to

the product installation directory.

ma_admin -u /opt/sybase/MA-15_0/my_inst

To upgrade all the instances in the current

product installation.

ma_admin -u all

To upgrade a specific instance in the current

product installation directory.

ma_admin instance=my_inst

OR

ma_admin my_inst

NOTE:

- The -u <src_instance_dir> provides the

ability to upgrade an individal instance

from a previous major release to the

current release.

- The 'all' or '<inst_name>' or

'instance=<inst_name>' upgrade options

performs an upgrade of instance(s)

in the current product release. All

upgrades are performed directly on the

instance to be upgraded. The Replication

Agent instance configuration file is

backed before the upgrade for use in error

recovery, if required. If an error occurs,

the upgrade is rolled back. This option is

intended for performing upgrade of instances

between release to release in the same

major release such as a patch update.

For internal use only(QA found the issue

before release):

Table or procedure can not be marked/unmark/

enable/disabled by using "pdb_setreptable"

or "pdb_setrepproc" due to "null" error.

provides two new API command, ra_deviceoffset

and ra_helpdeviceoffset to set the raw device

offset and provide help on the raw device offset

setting

BUG: PD 12.5.0.2361(esd#19) consolidate 'metamodel.oom' to ASE 1501 esd#1 using the Sybase ASE ODBC driver 15.00.00.xxx causes loss of metadata.

This issue appears to be due to the size specified in the 'text size' parameter of the ODBC DSN. The default value is 32678.

The consensus from a consult is that the 'text size' attribute needs to be increased to resolve this issue. Changing this value from 32678 to 10,000,000 should have no performance related issues when working with a repository installed on ASE. This value can be increased to a maximum of 2G if necessary.

Another issue that occurred was some text characters being extracted incorrectly. Using metamodel.oom, 'ellipsis' in a comment was extracted as a '.' period.

This is due to the character set of the server. However, this issue can be addressed by changing the 'character set' attribute on the ODBC driver.

ASE TSE has provided the following:

The ellipsis (...) character is properly processed (consolidate/extract/compare from repository)

when PD 125 client has MaxBytesPerChar set and the ODBC driver setting 'User Specified' = utf8 is set...

////////////////////

ASE:

I have an ASE 1501 ESD#1 server.

It's charset = iso_1, sort = bin_iso_1.

---

ODBC driver:

If I set the <<User Specified>> = utf8 in the Character Set groupbox

and the <<Client Default>> > Code Page Type = ANSI (it's greyed out).

---

PD 12.5 client:

The regkey: HKLM\Software\Sybase\PowerDesigner 12\Repository\MaxBytesPerChar =3

The ellipsis character (a unicode character) is properly mananged in the db.

'WK_TEST' and 'FLOWS_FILES' are now being filtered

out for replication by default.

primary database or the RASD is not yet

initialized, "pdb_setrepcol" with no argument

returns "0 rows affected" instead of returning

an error.

performance is slow.

Attempt to locate entry in sysdatabases for database 'database_name' by name failed - no entry found under that name. Make sure that name is entered properly.

the Replication Server may fall down with a 7035 error (additional allocation would exceed the memory_limit).

This can occur if the ASE and the Replication Server are both configured with multi-byte character sets.

with error "Too many open files".

may stop replication. There is a new

Replication Agent configuration

log_scan_eol_threshold for determining when to flush

sorted records that have not been checkpointed.

And in Oracle RAC environment, for helping to

determine when a node in a cluster is no longer

active.

log_scan_eol_threshold

The threshold used to determine when to flush

sorted records that have not been checkpointed.

Default

300

Values

An integer from 300 to 2147483647.

Comments

- The value of the log_scan_eol_threshold

parameter is the maximum number of seconds that

can elapse before the Log Scanner component

flush sorted records that have not been

checkpointed.

Notes

- For Oracle RAC, log_scan_eol_threshold

configuration is used in determining whether a

node in the cluster is active. Since a node

may go down at any point during replication,

Replication Agent has to determine when a node

is no longer active, and the

log_scan_eol_threshold configuration is used

for this purpose. If Replication Agent is

reading at the end of the node's redo log

thread and there are no checkpointed records

in the queue, Replication Agent will treat a

node as inactive after the number of seconds

specified by the log_scan_eol_threshold

configuration pass. The log_scan_eol_threshold

configuration can not be set too low, otherwise

Replication Agent treating a node as inactive

when it is actually still active.

correctly when using "Oracle Identity Manager

10.1.4".

There is a new Replication Agent command to

support use of Oracle Identity Manager.

Command:

pdb_send_osuser_list

Description:

Add or remove database user id to/from osuser

list. If the database user is in the osuser

list, then any transactions for that database

user will be sent as the relative operating

system user for that transaction user. This

list is a list of 'database' users that will

need to be replaced with the 'operating system'

user name. This is NOT a list of

'operating system' users. This command also

returns a list of the database users in the

osuser list.

Syntax:

pdb_send_osuser_list

pdb_send_osuser_list [[add | remove],[user | all]]

Parameters:

add The add keyword add user into osuser list,

whose transaction will be sent to

Replication Server as its relative

operating system user.

remove The remove keyword removes database user

from osuser list.

user The name of the database user that need

be converted to operating system user.

The user name is case insensitive.

all All database users will be converted to

operating system user if they have a

valid operating system user.

Examples:

Example 1 pdb_send_osuser_list

This command lists database users who will be

converted to osuser. Assuming a person logs

into their operating system as 慾oeuser�, and

subsequently logs into Oracle as 憉ser_a�:

Example 2 pdb_send_osuser_list add, user_a

This command adds database 'user_a' into

osuser list. The transaction of 'user_a; will be

sent as operating system user 慾oeuser�

Example 3 pdb_send_osuser_list remove, user_a

This command removes database 'user_a' from

osuser list. The transaction of database

'user_a' will no longer be converted to the

operating system user 'joseuser'.

Example 4 pdb_send_osuser_list add, all

The transaction of all database users will be

sent as operating system user

Usage:

- When pdb_send_osuser_list is invoked, its

function is determined by the keywords and

options you specify. When multiple keywords

and options are specified, each must be

separated by a comma. Blank space before or

after a comma is optional.

- Only session login later then

pdb_send_osuser_list will be

converted as osuser. The session by user

which is earlier than pdb_send_osuser_list

setting will not change.

For example:

pdb_send_osuser_list add, user

- The pdb_send_osuser_list command is valid

only when the Replication Agent instance is

in ADMIN state.

- If command without parameters to list only,

then it valid for any status.

with Filechannel Map failed Exception

when user initializes Replication Agent

and then re-initializes it on HPIA platform.

maximum, total, and free memory amounts (in bytes)

in the log file during initialization and when

ra_version_all is invoked.

handled correctly when the primary database

is IBM UDB 9.5.

are out of synch.

after a 'resume' command if there are a lot of

archive logs stored in Oracle ASM.

Collection task failed and will be skipped. Message=null

is upgraded to SP3, some Replication Agent system

objects are overwritten. Please use ra_migrate

command to restore these missing objects.

are out of synch and the Replication Agent system

log contains a warning message indicating that the

log sequence number for the second block in the

log does not match the log header sequence number.

with error "LTI start replication

failed to initialize connections",

after Replication Server is upgraded

to 15.2.

are out of synch or an open transaction prevents

the truncation point from moving and also results

in the Replication Server stable queue filling up.

for Replication Agent. The workaround is that zero

the locator of RASD by Replication Agent command

'ra_locator zero' and zero the locator of

Replication Server by Replication Server command

'rs_zeroltm <data_server>, <database>'. Before

doing this, please make sure that all the data

have finished replication. Then resume Replication

Agent again.

1.install repository on ASA10 by JDBC , after executing scripts a few time, it pops up an error window says that "SQLSTATE = 23502 SQL Anywhere Error -195: Column 'CMMT' in table 'PMUSER' cannot be NULL".

This issue only happens when using PD EBF6 to install repository directly, if the repository is installed by some older versions and use PD BEF6 to upgrade, it works fine. And if install by ODBC directly, it works fine too.

Specifically, the customer would like to view the extended attributes associated with objects.

The customer uses extended attributes extensively throughout their models. With the introduction of CMR, they would like to the extended attributes exposed. The lack of this exposure limits the effectiveness of the CMR application for their company.

Their intention is to use CMR to allow 300+ users to view metadata associated with their models. Without the extended attribute a large portion of this information is missing.

new version. As a result, there are no fixed

bugs to list in this section.

configuration for scanning the primary database

redo log threads in parallel.

Configuration Parameter Name

lr_parallel_scan

Description

The lr_parallel_scan configuration property is

applicable to Oracle RAC only and determines

whether the redo log threads for all nodes in a

clustered database are scanned in parallel or

whether a single serial scan is used.

Default

false

Values

true, false

Comments

- When true, the Replication Agent will start a

redo log scan thread for each redo log thread in

the clustered database.

- When false, the Replication Agent will do redo

log thread reads for each redo log thread in the

clustered database serially.

been added to improve RAC replication latency.

The feature is configured and monitored using

the following API commands and properties.

Configuration property:

pdb_commit_generation

Values: true or false

Default: false

Description:

If pdb_commit_generation is set to true,

Replication Agent will generate committed

transactions in the primary database at a

configured interval.

Configuration property:

pdb_commit_interval

Valid values: 1 to 5 seconds

Default: 1 second

Description:

pdb_commit_interval is the interval, in

seconds, at which the committed transactions

are generated in the primary database.

Command:

pdb_commit_generation_status

Description:

The command returns the status for all

primary database commit generation threads.

Command:

pdb_commit_generation_filter <action>,<inst>

Values:

action is the keyword 'add' or

remove',

inst is the valid Oracle instance

name, or the keyword 'all'

Description:

If the keyword 'add' is passed as an

argument, Replication Agent will add the

instance to the filter list, disabling the

commit generation for the instance.

If the keyword 'remove' is passed as an

argument, Replication Agent will remove the

instance from the filter list and enable the

commit generation for the instance.

When the command is called without any

arguments, then the names of all filtered

instances are displayed.

displays incorrect descriptions for 'pdb_skip_op'.

this DVRE table need to be build for Distributor (DIST)

So, this query executed only once per Distributor.

(you may find 1 Distributor for each Primary connection).

take effect when auto_mark_tables is true.

'pdb_setrepproc' command with 'unmark, all' option

does not set the unmarked object to 'disable'

status.

provide datatype mapping for Replication Server

15.2 are missing. These files are installed under

the config directory and are used to automatically

generate replication definitions.

New Select Privileges required

The select privileges for the following Oracle system tables in the primary

database server must be granted to the Replication Agent pds_user_name/user:

� SYS.TAB$ � required to support table replication

� SYS.MLOG$ � required to filter out materialized view log tables

� SYS.TABPART$ � required to support partitioned table replication

� SYS.TABCOMPART$ � required to support partitioned table replication

� SYS.TABSUBPART$ � required to support partitioned table replication

� SYS.NTAB$ � required to support table replication

� SYS.IND$ � required to identify indexes

� SYS.INDPART$ � required to identify indexes

� SYS.INDCOMPART$ � required to identify indexes

� SYS.INDSUBPART$ � required to identify indexes

� SYS.LOBCOMPPART$ � required to support partitioned LOB replication

� SYS.LOBFRAG$ � required to support partitioned LOB replication

� SYS.TS$ � required to identify tablespace encryption in Oracle 11g

� SYS.SNAP$ � required to filter out materialized view tables

multiple pre-15.1 Replication Agent instances to

current release, the upgrade process will fail to

upgrade the subsequent Replication Agent instances

with error "SQL Anywhere Error -103: Invalid user

ID or password".

Replication Agent instance (trigger-based

Replication Agent) to current release will fail

with error "No verifiable instance <rep_inst>

exists in directory <...>".

Replication Server 15.2 connection

to the replicate are missing from the

$SYBASE/RAX-15_2/scripts (UNIX)

or %SYBASE%\RAX-15_2\scripts (Windows)

directory.

while processing a chained operation that is

rolled back.

A)

1) batch set to 'on' ... alter connection to ms2k5srv.mssqldb set batch to 'on'

B) required settings that are missing from our doc presently

2) ecda_service_to_ms2k5srv.mssqldb

{Target Interaction}

DelimitSqlRequests=yes

3) dsi_cmd_seperator set to ';' ... for ms2k5srv.mssqldb connection only ...

alter connection to ms2k5srv.mssqldb set dsi_cmd_separator to ';'

... if this is set globally will cause definite problem with rssd stored in ASE

C) required settings that are mentioned seperately in our doc ...

it would be nice if all this was together in at least one place in our doc ...

4) {Client Interaction}

Transaction Mode = long

5) {Target Interaction}

allocate = connect

SQL transformation = Sybase

D) also PSE was seeing different results with the two options for ODBC drivers provided

by Microsoft on Windows if the customer is using ecda on the windows platform. so

we should maybe mention that customer might want to test both of these drivers to

see if one driver would work better than the other.

6) SQLSRV32.DLL ... this driver is most like the datadirect IVMSSS23.DLL

7) SQLNCLI.DLL ... this is another odbc driver Microsoft provides on windows

Feature of RAX15.3

Primary/Replicate

Databases Re-synchronization.

when Replication Agent is initialized with

pdb_dflt_object_repl configuration set to false.

filtering by Oracle SCN number.

"ra_config pds_dac_port_number" command

will return an error "Could not find Resource

Bundle containing index: PDS_DAC_PORT_NUMBER".

after issuing "pdb_setreptable all,disable"

command.

may fail with error "Invalid object name

'ra_xlog_system_'" when migrating pre-15.1

Replication Agent to the current release.

thrown during LOB processing.

Minutes an longer until PD came back. It seems that it take 5 Minute until the Repository tree in the browser is build up and the PD user can work again.

instance creation fails if the pds_password

configuration property contains lower case

characters.

file using ADMIN utility (ra_admin or ma_admin)

fails with Oracle 11g.

message when attempting to resume replication

before migrating the instance. The error returned

is "Transaction LogReader Initialization Failed".

Server is not initialized by 'pdb_xlog init'.

Instead, a new command 'server_xlog init' is

introduced to initialize the server.

Description:

Initialize or cleanup the server xlog.

Syntax:

server_xlog [init | remove] [,force]

Usage:

-When you want to initialize the server xlog,

you should run 'server_xlog init'

-When you want to cleanup the server xlog,

you should run 'server_xlog remove, force'

-Moreover, 'pdb_xlog init' will check whether

server has initialized. If not, pdb_xlog

won't run and prompt the user to run

'server_xlog init' first.

Replication Agent may take a long time to complete.

incorrect column name information.

'<table>, enable' fails. Replication Agent treats

'enable' as a table name and not a reserved keyword.

when they are in-row and the LOB is updated

with more than 4KB of data.

command with an invalid date in months does not

return an error.

"QueryException: Offending SQL statement" if

the database name is a reserved keyword in the

Replication Server System Database (RSSD).

2. If a table or column has a korean character, the charater is broken in the repository database.

3. The ct insist that some tools, such as pb, support dbcs(korean) for us7ascii charset.

And they want to PD reverse feature & repository with us7ascii charset.

replicate all the LOB data when inserting more

than 10mb of data into a table containing a BLOB

column.

trace "on",DSI,DSI_NO_LOG_SKIP_TRAN

go

This trace can also be added into the .cfg file.

Replication Agent System Repository.

the Replication Agent when the LOB is updated.

with an IllegalStateException for error "Cause

already initialized".

or Bound Connection transaction causes duplicate

key error similar to "Cannot insert duplicate key row

in object 'lr_reptran_' with unique index

'lr_reptran_x1'".

The customer is requesting the following:

Add feature to control the 'Manage All Documents' right; to be able to assign it to either the root or a specific branch and/or to a specific folder. Once the 'Manage All Documents' right is assigned to a user or group, that user/group can create a folder in any other folder even though he has list or read rights. PD needs to be able to offer more flexibility for the permission control to a folder or branch that way they can designate specific group or a specific user document control within a specific end user environment.

Here is a simplified scenario at our company:

We have 3 folders in this repository (at Default branch): Baseline, CAO, and OPC.

We would like to create a manager to be able to create users and manage only the documents within the OPC folder.

Once the 'manage all documents' is applied to the user, they can add/change folders and documents in other folders in which

they do not have write or full permissions.

Repro:

1. Log into repository with 'ADMIN'

2. Create 3 folders all at the root/Default branch.

REPOS::ADMIN::<Default>

Baseline (folder)

CAO (folder)

OPC (folder)

3. Create a user "testmanager" with the following rights:

Connect, Freeze Versions, Lock Versions, Manage Branches, Manage Configurations, Manage All Documents

note: You could do this with just the 'connect' and 'Manage All Documents' rights as well.

4a. select "REPOS::ADMIN::<Default>" branch in repository browser.

b. right-mouse button (RMB) click <Default> branch and select "Permissions" menu.

c. select 'Show All Authorized User's icon.

d. select the 'testmanager' row and then his permission to 'List'.

e. select the 'Copy Permissions to All Children' which will push this permission down to all other items in this <Default> branch.

5. select OPC folder and right-mouse button (RMB) click it > Permissions and set 'testmanager' to Write or Full.

6. select either Baseline or CAO folder and right-mouse button (RMB) click it > Permissions and you see that 'testmanager'

is set to 'List'

7. Try and add a folder to either Baseline or CAO folders. It is allowed.

The problem is he has rights to manager all documents in the repository and can assign permission to users in all objects in the repository. The user would like PowerDesigner to restrict him only to manage OPC folder. If they give the 'testmanager' "Manager Users" rights, they only want 'testmanager' to be able to assign rights to users within the OPC folder only. In other words, we want local administrator has local rights only.

article cache access stops replication.

screen contains an incorrect EBF

ONE-OFF id.

to correctly process an alter table

drop UDD or Xml column.

is not prevented when processing an 'alter table'

DDL command.

state with an IllegalStateException when updating

an off-row LOB column in a table with both

BLOB/CLOB and long/long raw columns.

table' DDL command, the LOB replicate status

for the altered table is updated incorrectly.

Using repdef datatype "time": 'ORA-01841: (full) year must be between -4713

and +9999, and not be 0'. Using repdef datatype rs_oracle_timestamp6:

'ORA-01843: not a valid month'.

user executes sp_recompile in primary database.

Stereotype should be visible on general tab of repository property sheet

For quick lists, it would be more useful/helpful to see simple details of a column at the column list level of the table (name, code, datatype). We realize that viewing this same metadata connected to the repository in the PD Client interface also presents the same behavior. However, having name, code, datatype and possibly the domain is certainly more useful when seeing the (quick) list of columns on a table than having to drill down into the attributes tab to see even more details of the column object.

Unconverted bytes changed to 'inverted question mark (� U+00BF).

The Check In window does not show deletion.

when LD_LIBRARY_PATH_64 environment setting

is defined in the environment.

Step 6 states the following:

6. Restore any 3rd party class libraries from the backup in Step 3.

The problem is that the CMR directory does not exist in the webapps directory.

In order to rebuild the cmr directory, you must first restart the server.

Step 5a should be something like:

restart the application server which will rebuild the cmr directory structure.

This would then be followed by step 6.

the mirrored device path information set by the

ra_devicepath command is not retained.

Authenticating a Replication Sever before its ASE servers have been authenticated causes a Null Pointer Exception to occur.

executing 'ra_locator update' causes Replication

Agent to throw an exception.

replication definition for a table containing

an OBJECT column.

are replicated to replicate database when primary

data base is in warmstandy mode and

Replication Agent "filter_maint_userid" property

is set true.

name backup directory

name does not match

backup timestamp.

RepAgent initialization fails

in Oralce RAC environment.

rs_ticket processing in the Replication Agent

system log.

without the force option can be executed

successfully even if marked user tables and

procedures still exists.

rs_create_repdef when Replication Server is not

accessible.

load ASM disk mappings from the property file into

the repository.

Upgrading or Downgrading an Existing Replication Server

Replication Server� 15.2 for UNIX

Document ID: DC35817-01-1520-01

Last revised: February 2009

...

5.

If the Replication Server uses embedded RSSD, edit the rs_name.cfg file,

where rs_name is your Replication Server:

Add the erssd_release_dir parameter to specify the location of the pre-

upgrade SQL Anywhere. For example:

erssd_release_dir=/work1/sybase/REP-15_1/ASA9

Add the erssd_start_cmd parameter to specify the command to start ERSSD.

Obtain the name and location of the Replication Server you are upgrading,

and the port number of the Replication Server RSSD, from the interfaces

file. You can find an example of the parameter in the Replication Server

log file by searching for 揈RSSD start command�. For example:

erssd_start_cmd=/work1/sybase/REP-15_1/ASA9/bin/dbspawn

-f -q /work1/sybase/REP-15_1/ASA9/bin/dbsrv9

-ct- -ti 0 -x "tcpip(PORT=11751;DOBROAD=NO;BLISTENER=NO"

-o /work1/sybase/REP-15_1/samp_repserver/errorlog/SAMP_REPSERVER.out

/work1/sybase/REP-15_1/samp_repserver/dbfile/SAMP_REPSERVER.db

...

the following line should have a closing parenthesis...

-ct- -ti 0 -x "tcpip(PORT=11751;DOBROAD=NO;BLISTENER=NO)"

they added the following...

errsd_release_dir=...

errsd_start_cmd=...

they should have added the following spelling...

erssd_release_dir=...

erssd_start_cmd=...

the upgrade process proceeded and gave an error...

CONNECTIVITY ERROR: CT-Library error: 'ct_connect(): network packet layer: inte

rnal net library error: Net-Lib protocol driver call to connect two endpoints f

ailed'.

Press <return> to continue.

LTL-formatted string to Replication Server for a

timestamp in a user-defined datatype when

pdb_convert_datetime is set to true. This causes

the Replication Server DSI to go down.

fails with error "No entry exists for id <XXX>".

execution of additional commands such as 'create replication

definition', 'drop subscription', etc. may result in a deadlock in the

RSSD. To recover from this behavior, restart the Replication Server.

throws a NullPointerException when the

ra_truncatearticles or rasd_trunc_schedule 'force'

command is executed twice.

fails due to insufficient privilege attempting

to select on the audflags,deftabaud,defvwaud,

defpraud columns against the master..sysdatabases

table and the password column against the

master..syslogins table.

returns an unformatted error message "The last

saved truncation point <{0}> is less than database

truncation point <{1}>." when attempting to save

the truncation point that is less than the

database truncation point.

1.go to search after login

2.click any model and input "AnyMetaClass:AnyMetaAttribute LIKE *a*" to search

no result return and there is an error in the tomcat as follows:

definition is not automtically dropped when table

is unmarked for replication or table is dropped.

NullPointerException when trying to dump detail

information of problem log record.

-> A Prompt for Overwrite if document exists as read-only Version locally.

-> A popup Error Message, when Write to File fails.

-> Clean up the different behavior of Treelist and Menu Options

-> Do not offer Merge Document if User has read-only authorization.

Replication Server to fail with error

"Failed to convert from char type to

numeric type" when replicating with Dynamic

SQL option enabled. It may also cause error

"No value or default value available and

NULL not allowed" when DSI Bulk Option

is enabled.

type is not processed correctly.

I. 2009/04/01 14:16:43. Replication Agent version (710) for 'ds.db' does not match the default LTI version for this Replication Server 700 using version 700.

...

*** Executing SQL statement 20:

alter table PMBPMS add AVSN varchar(254) null

[Microsoft][SQL Native Client][SQL Server]Statement(s) could not be prepared.

SQLSTATE = 37000

*** Executing SQL statement 27:

alter table PMDVTL add AVSN varchar(254) null

[Microsoft][SQL Native Client][SQL Server]Statement(s) could not be prepared.

SQLSTATE = 37000

'ra_dumptran' that allows the user to obtain

detailed information about database operations

and database operations in a transaction by

specifying the Oracle transaction ID.

Command ra_dumptran

Description:

Command ra_dumptran dumps all operations for a

specified transaction to an exclusive log file

in order to help trouble shoot a failed

operation, or transaction. The time the

transaction was executed, the user that executed

the transaction, the name of the log the

transaction was dumped to, and additional

database specific information is displayed as a

result set.

If the Oracle script

$ORACLE_HOME/rdbms/admin/dbmslm.sql

has not been installed at the primary database,

an error will be reported indicating it must be

installed in order for the ra_ dumptran command

to properly operate.

If the new permissions that must be granted to

the "pds_username" are not granted at the time

ra_ dumptran is executed, an error will be

reported indicating the following permission's

must be granted before the ra_ dumptran command

will properly work:

EXECUTE_CATALOG_ROLE TO PDS$USER;

SELECT ON V$LOGMNR_CONTENTS TO PDS$USER;

SELECT ON V$LOGMNR_LOGS TO PDS$USER;

SELECT ANY TRANSACTION TO PDS$USER;

If a public synonym that must be created for

"SYS.DBMS_LOGMNR" is not created, an error will

be reported indicating that "DBMS_LOGMNR" does

not exist.

CREATE PUBLIC SYNONYM DBMS_LOGMNR FOR SYS.DBMS_LOGMNR;

Syntax: ra_dumptran "opid | locator | xid"

Opid - The Replication Agent operation id for a

database operation

Locator - The Replication Agent locator for a

database operation

Xid - The Oracle transaction ID for the

transaction

Example 1:

ra_dumptran

0x0000.01542e48.0001:0001.000002dc.00000004.0010

This command returns information for the begin

operation in the transaction specified by an

operation ID.

Information for every operation in the transaction

is written to a file in the Replication Agent log

directory. The file is named with the prefix

"XID" followed by the transaction ID and ".log".

Example:

$RAX_DIR/<INSTANCE_NAME>/log/

XID0005.002c.0000002c.log

Example 2:

ra_dumptran

0000000001544ada00060001000002de00000008001000000

000000000000000

This command returns information for the begin

operation in the transaction specified by an

locator.

Example 3:

ra_dumptran 0x0007.002a.000032f0

This command returns information for the begin

operation in the transaction specified by a

transaction Id.

Usage:

The ra_dumptran command returns the following

information for the begin operation specified by a

locator or operatin ID:

- The Replication Agent operation id for the

transactions begin operation in the format:

wrap.scn.subscn.thread.lsn.block.offset

- The Oracle SCN for the transactions begin

operation as logged in a redo log file

- The Oracle id for the transactions begin

operation

- The name of the user that executed the

transaction

- The date and time the transaction executed

- The Oracle thread that transaction was executed

on

- The Replication Agent command that will cause

the transaction to be skipped by the Replication

Agent while replicating

- The name of the file the transaction is written

to

The ra_dumptran command wtites the following

information for for all operations in

the transaction specified by a locator or

operation ID:

- The Oracle SCN for the operation as logged in a

redo log file

- The Oracle thread that operation was executed

on

- The Replication Agent operation id for the

transaction begin operation in the format:

wrap.scn.subscn.thread.lsn.block.offset

- The Oracle id for the object the operation

affected

- The Oracle name of the object the operation

affected

- YES if the object in the operation is marked

for replication by the Replication Agent, No

if it is not marked for replication

- The operation type, i.e. INSERT, UPDATE, DELETE

- The Oracle SQL statement for the operation

Replication Agent supports

replication from Oracle

archive logs only (no online).

Add new LTL trace to trace

begin/commit/rollback only.

The trace name is LTITRACETRAN.

that will be entered whenever an error occurs

during Replication. In addition, all commands

and properties that were restricted to ADMIN

state are now also editable in Replication Down

state.

command, ra_deviceoffset and ra_helpdeviceoffset

to set the raw device offset and provide help on

the raw device offset setting.

rasd_restore sometimes fails to restores the

Replication Agent System Data Repository.

rasd_restore sometimes fails to restores the

Replication Agent System Data Repository.

Invoking 'rasd_trunc_schedule' command with an

invalid date in months does not return an error.

Invoking 'rasd_trunc_schedule' command with an

invalid date in months does not return an error.

securefile LOB and LOB fragment

defined in encrypted tablespace

is successful when it should not

be allowed.

after attempting to add a schedule date for every

31st day. The schedule looks like "* * 31 * Mon".

execution time to the next hours/minutes beyond

the current hours/minutes if the hours and minutes

fields in the schedule have multiple values. When

the schedule time is not the current date, and

the smallest value contained in the schedule is

smaller than the current time, the next execution

time picked up by Replication Agent is not the

earlier time in the schedule.

may take a long time to complete.

PowerDesigner Error:

Missing Parent Relationships (Object without parent): 6344

There is very little to go by to troubleshoot and address such a problem. Especially, when the ct. cannot provide their model or repository database to us.

Here is the full message presented to their PD client in the Output windowpane:

Checking in the document

'D:\Documents\DataModeling\PD15test.oom'

- Freezing the repository document before check in...

- Checking out the repository document 'PD15test'...

The check in of the document has been cancelled.

Checking in the corrupt model in a connection to the Repository without using the Proxy throws and Error and Powerdesigner keeps on reacting

LD_LIBRARY_PATH_64 is set and does not contain the correct pathnames.

To work around this issue, prior to starting 'rs_init', merge the values

of the environment variables LD_LIBRARY_PATH and LD_LIBRARY_PATH_64 and

set both environment variables to this merged value.

indicate that the installer should start the SAMPLE_RS during a silent

install, the installer fails to do so.

of the SAMPLE_RS, the subsequent installer panel incorrectly enables the

'Previous' button and allows the user to navigate to the previous panel

to create the SAMPLE_RS again.

completes with non-critical errors, the contradictory messages 'Press

Done to quit the installer' and 'PRESS ENTER TO EXIT THE INSTALLER' are

incorrectly displayed.

the user for the location of a Replication Server 15.5 license file.

Thus, the installer is unable to install the license file for the user.

To work around this issue, after the installer completes successfully,

the user can manually copy the license file to the directory

'$SYBASE/SYSAM-2_0/licenses'.

error messages '(HVAR Error) ...' may appear in the Replication Server

error log. To recover from this behavior, issue the 'create replication

definition' command with the 'send standby' clause for the primary table

referenced in the error messages.

insufficent privileges during Replication Agent

initialization lists 'EXECUTE on DBMS_LOCK'

privilege twice.

by issuing "pdb_xlog init, force" command causes

rs_ticket to stop working.

when rescanning a DML log record on a table

containing a LOB column.

stops replication.

"Processing has not completed for chained op"

sends Replication Agent into the ADMIN state.

"find ${SYBASE} ! -perm -200 | xargs chmod u+w" to workaround.

cdb ...' command does behave as expected.

replicated table name or replicated column name is specified with quoted

identifiers.

*** Executing SQL statement 7001:

insert into PMENUM(CLSS,ENID,VALU,RVAL) values(1421, 1, '€', 'EUR')

Error converting characters into server's character set. Some character(s) could not be converted.

End result is that the repository is not created.

Workaround:

Use an ODBC connection to create the repository

Add a section giving examples that show the nuances of combinations between a MSA_dbrepdef and table rep defs...

The main point is to communicate that one should be careful. The best choice is to explicitly specify the OWNER of the table in table rep defs and use sp_setreptable with owner_on to prevent any unsuspected results...

When PD is launched, you are able to connect to the repository via an ASE native driver profile. If you disconnect from the repository and attempt to connect a second time, the repository connection fails. The reported error reads:

Unable to initialize Client Library context.

The problem appears to be introduced after the first disconnection from the repository. As long as I do not disconnect from the repository, I can make multiple ASE connections using the native driver. for example, I am able to reverse engineer a database and I can connect, disconnect and reconnect without issue.

because the Replication Server incorrectly treats the JAVA column as an

IMAGE column. To work around this behavior, mark the table as

non-compilable.

cdb ...' command does not behave as expected. Under certain

circumstances the 'sysadmin cdb ... dump_i ...' command will return the

error message 'Error occured while processing 'sysadm cdb' command'.

When HVAR is disabled, the 'sysadmin cdb ...' command is incorrectly not

disabled.

Workaround:

open the MMR in the workspace and then consolidate the mmr.

C:\oc15e7\OCS-15_0\bin>isql -Ss6s1254e91ss -Usa -P -w2048 -Drs3s151ss_rssd

1> select @@version

2> go

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

Adaptive Server Enterprise/12.5.4/EBF 16816 ESD#9.1/P/Sun_svr4/OS 5.8/ase1254/2146/

64-bit/FBO/Wed Apr 15 14:39:31 2009

(1 row affected)

1> rs_helprep test123456789012345678901234567890_rd

2> go

Msg 103, Level 15, State 1:

Server 's6s1254e91ss', Line 1:

The identifier that starts with 'test12345678901234567890123456' is too long. Maximum length is 30.

1> rs_helprep 'test123456789012345678901234567890_rd'

2> go

1> quit

C:\oc15e7\OCS-15_0\bin>

White/gray area replaces the "Compare Models" dialog while comparing local model with repository.

one primary db with two db replication definitions each with filters and each replicates to a seperate replicate database. if the 2nd db repdef's filter is modified by RM or isql, the 1st db repdef's filter stops working.

2009/11/30 12:36:55 ASA Warning 120: 'tsql_outer_joins' is an unknown option

This is just a warning and the upgrade completes successfully.

message 'ASA Error -141: Table rs_update_thread ...' may appear in the

Replication Server error log. This behavior is caused by Replication

Server issuing an incorrect command to the internal ASA server embedded

within the IQ server. To recover from this behavior, connect to the IQ

server and issue the 'grant execute on rs_update_thread to public'

command.

an Oracle LOB causes an OracleRuntimeException to

occur which stops replication.

Check in a model in the repository. Compare local model with repository. PDes has detected slight differences on Position and Size on objects.

It occurs only when check in mode is Update, through a Proxy connection. No problem using a Direct connection.

The ASEP handles this situation in a graceful way and switches to using the iso_1 code page. It would be great if the RMP would do the same graceful handling of this same situation.

Replication Server� 15.2 Administration Guide: Volume 1

DOCUMENT ID: DC32511-01-1520-01 LAST REVISED: February 2009

Explain the limitation of java/jdk excluding support for roman8 code page when Sybase Central and RMP Replication Manager Plugin are used in conjuction to attempt a login to an ASE/RepServer server that is using the defualt code page of roman8.

The customer needs to be aware that even though roman8 is listed in the drop down list of possible code page choices when making a server connection in the dialogue where the username and password are being requested ... choosing roman8 as the manually select code page will cause a connection failure since java/jdk excludes support for the roman8 code page.

with errors like "Pid <pid> was killed

due to failure in writing to user

register stack - possible stack

overflow." when command "pdb_xlog init"

is executed on HPIA 64-bit machine.

the customer is thinking this showing him how much space is being held up in the

inbound queues by transactions that still need to be removed from the stable queue

and delivered to the dsi ... replicate ds.db

Refer to CR 611419

the customer is thinking the present "size" column is showing him how much space is

being held up in the inbound queues by transactions that still need to be removed

from the stable queue ... it would great if we could rename the present column to

"# of segments in use" and create a size column based on the difference between

Last Seg.Block and First Seg.Block ... also when Next Read is after the Last

Seg.Block this confirms the inbound queue is drained completely.

and delivered to the dsi ... replicate ds.db

by frequent access to the Replication Agent

System Repository (RASD) while processing

operations on tables that are not being

replicated.

are now logged only if RACONTRC trace is enabled.

For example:

Default

->Folder

->->Project Management(CDM).cdm - v1

->->-> Project Management(CDM) - v1

Note: first reference includes model extension

Using the following steps, I was able to reproduce this issue:

Created a brand new database instance on MS SQL Server 2005

1) install PD15.0.0 GA

2) create repository

3) in repository, create folders CDM and PDM

4) open project.cdm and check-in to CDM folder

5) open project.pdm and check-in to PDM folder

6) in repository, create user tony

7) install CMR 15.0 GA

connect via CMR using login tony (same results using ADMIN login)

The customer's document, includes screen shots showing the list of configurations. In one image, the Associated Folders field is blank for all configurations. In the second image, three configurations have an associated folder listed. In both images, the customer is connecting to the same repository with the same user. The only difference is that they are using two different PC clients.

Using the following repro, I get similar behavior.

Repository structure is

ROOT

-CDM Folder

--CDM model

-PDM Folder

--PDM model

To reproduce:

1) Connect to repository from PC_1 using ADMIN login

2) Right click on existing folder and create configuration

3) Select Repository -->Configuratiosn and display Associated Folder column Note: the column is populated

4) Connect to repository from PC_2 using ADMIN login

5) Select Repository -->Configuratiosn and display Associated Folder column Note: on PC_2, the folder name has become Folder_1 杤1.1 while on PC_1 it is CDM 杤1.1

For this repro, the configuration was created on a Vista workstation (PC_1) with MS SQL Server as the backend. The version of the SQL Server driver version is 6.00.6002.180005.

For PC_2, a XP workstation is used and the SQL Server driver version is 2000.85.1132.00.

Connected to repository from a third workstation using a different database login and SQL Server driver version 2000.85.1132.00. The connection displays the Associated Folder the same as PC_1.

For the customer they are reporting that the associated folder information is missing. While on the phone teh customer was able to repro this on 15.0.0.

The repository objects do not have attributes. They only have properties.

mirror paths as 'NOT_CONFIGURED'.

a table containing more than 8 text columns.

If the same is done in Firefox 3.5.7, the vertical scrollbar maintains the current position.

a NullPointerException is thrown from

OracleDatabaseContext.getID when Replication Agent

attempts to resume replication after a restart.

checkin the model in an ASE repository using proxy connection

Because of no support of "Max byte per char"

instrumented triggers fail to open cursors

in the same user session after it is fired

for a SQL statement affecting no rows.

reading from the device offset value set in

the ra_deviceoffset command when the

log_read_block_count configuration property

is set to a value greater than 1.

For example, if a MS Word document or Excel spreadsheet is checked-in to the repository, when they select this link in CMR, they would like/expect to see the contents of the MS Word document or spreadsheet.

state with IllegalArgumentException from

ds.ase.device.Page.getBufferSlice() error.

caused by network issue.

installation of the Unified Agent Framework.

Log Reader statistic "Last page scanned" which

displays the most recent page scanned from the

device log.

Log Reader statistics for ASE

Component Statistic Description

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

LR Last page scanned Block and page number

of most recent page

scanned from log

devices.

page while ASE is already writing to a new log.

incorrect truncation point value displayed

for a move truncation point trace message.

installation of the RMS Agent for the Unified Agent Framework.

replicate any and all grouped transactions. In order to replicate them

successfully, Replication Server is forced to ungroup the transactions.

and reports "java.lang.IllegalState Exception:

No applicable system object found" for DDL

commands when processing large create global

temporary table DDL commands in the redo log.

NCHAR data correctly when there is both a database

level and a table level replication definition.

The customer feels that the SVG option is not enough. They would like the ability to resize the control area where the diagram is viewable.

state when replicating an insert or update for a

table containing a nested table column.

command is executed, Replication Agent

fails with a NullPointerException.

accumulating SySAM unserved licenses if there is

more than 1 license file with unserved CPU

licenses.

To reproduce:

1) create a repository

2) create the following folders in this order

a) zeta

b) alpha

c) theta

d) beta

3) refresh the repository browser NOTE: the folders are sorted in alpha order

4) consolidate or extract a model

5) In the Check-In or Check-out window, select a Folder

NOTE: the folders are listed in the order that they were created

REPLICATION DOWN state because a table replication

definition is not found. This will occur if both

the column_compression and ltl_send_primary_keys

configurations are enabled and if a database

replication definition does not exist.

'%SYBASE%\REP-15_5\doc\errmsg.sub' are re-named

'%SYBASE%\REP-15_5\doc\error_messages_rs' and

'%SYBASE%\REP-15_5\doc\error_messages_subcmp',

respectively.

when using rs_helpuser in the RSSD and a user has been granted both ...

connect source

create object

... permissions the one may see the following incorrect result ...

isql -Srs3x152e11sx_erssd -Urs3x152e11sx_RSSD_prim -Prs3x152e11sx_RSSD_prim_ps -w2048

1> rs_helpuser

2> go

Users and Privileges Known at Site rs3x152e11sx

Primary Users

User Name Permission(s) Name

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

...

rs3x152e11sx_rsi create source, create object

after moving the truncation point and setting the

value of the LTM Locator stored in both the

Replication Agent and the Replication Server to

zero.

value to itself is replicated as partial update.

This message should be printed out as an informational message.

fails with Incorrect syntax near '@tabid' error.

customer's who setup MSA replication can possibly encounter the following

situation.

The dsi to the replicate abnormally stops because the ASE log on the replicate

fills up and requires manual intervention to get the secondary trunc point

removed ... the customer wishes they had been alerted to this situation

by the documentation

add instructions to remove secondary trunc point from replicate MSA db log

here is the present documentation...

****************************************************************************************

****************************************************************************************

Replication Server� 15.2

Document ID: DC32511-01-1520-01

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc32511.1520/

html/rsadmin_vol_1/rsadmin_vol_1540.htm

Chapter 12: Managing Replicated Objects Using Multisite Availability

Subscription with bulk materialization

...

1.Dump PDS.pdb. The DSI connection to the replicate database is suspended when the dump marker reaches the replicate Replication Server. It is suspended so that no data will be replicated until you finished step 2. Replication Server activates and validates the subscription automatically when the dump marker is replicated.

WARNING! Do not activate subscription or it will override the wait for dump marker at the Replication Server.

2. Load PDS.pdb to RDS.rdb.

3. Resume the DSI connection to the RDS.rdb.

****************************************************************************************

****************************************************************************************

here is a proposed set of instructions for the documentation change...

Chapter 12: Managing Replicated Objects Using Multisite Availability

Subscription with bulk materialization

...

After you define the subscription:

1 Dump PDS.primary_db. The DSI connection to the replicate database is

suspended when the dump marker reaches the replicate Replication

Server. It is suspended so that no data will be replicated until you

have finished step 2. Replication Server activates and validates

the subscription automatically when the dump marker is replicated.

Warning! Do not activate subscription or it will override the wait for dump

marker at the Replication Server.

2 Load PDS.primary_db to RDS.rdb.

3. Online RDS.rdb

4. Prepare the RDS.rdb as a replicate:

release the secondary truncation point with dbcc settrunc ('ltm',ignore)

optionally, disable the Replication Agent

dump the transaction log

5 Resume the DSI connection to the RDS.rdb.

state with an error message similar

to 'IllegalArgumentException: Invalid starting

row for page' after resuming.

Cannot drop the table 'rs_updown_status', because it doesn't exist in the system

catalogs.

To workaround this issue, a dummy table rs_updown_status should be created in the RSSD and upgrade should be re-done.

"Transaction LogReader received notification of an

unexpected Thread Death ..." error.

The "Syntax" part which list a summary of all parameters usable for "rs_subcmp" command, paramter "-h" and "-H" are missing.

Theses 2 parameters are present in the "Parameters" part which describe in detail usage of each parameter.

maintenance user was not filtered when

filter_maint_id was true.

turned on until after the Replication Agent is

started up, the error 'Supplemental logging is

not enabled for the primary database <orcl>'

would be complained when the user execute

'ra_admin init' to initialize the Replication

Agent system objects in the primary database.

But actually, the supplemental logging has already

been turned on.

This is expected behavior. In the Check-in window, only models listed in the <project> directory will be checked-in.

the customer desires to see the reference of the model shortcut in the repository browser.

To reproduce:

In your workspace,

1) create 2 projects, Project_A and Project_B.

2) In Project_A you create a new model, Model_A.

3) In Project_B you create new model, Model_B, and you add Model_A from Project_A.

We will have in Project_B a shortcut to Model_A:

Project_A

Model_A

Project_B

Model_B

shortcut to Model_A

Now we check-in both projects in the repository. If we look in the repository we will see the following :

Project_A :

Model_A

Project_B

Model_B

Note: that we don't see in the Project_B the shortcut to Model_A.

However if we checkout Project_B and select "check out dependencies" we will get :

Project_B

Model_B

shortcut to Model_A

*** Wed May 05 2010 15:14:56 GMT-0400 (Eastern Daylight Time) *** ahill ***

This enhancement request has been reviewed by engineering and will not be implemented.

This is expected behavior

As there is not repository model object for the shortcut, PD cannot display a node in repository browser for it.

state with IllegalArgumentException error during

resume when Mirror Replication Agent is configured

for multi-block read.

Customer create a repository in V12.x using Studio Enterprise eval. They later purchased DataArchitect Enterprise. They have upgraded to v 15.1 EBF8. When they attempt to connect to the repository via CMR, they get an error. In the log file, there are errors stating problems loading the OOM, RQM, and BPM metaclass. Upon review of the customer's PMLIBR table, the OOM, RQM, And BPM versions are at 12.1 or 12.5.

Since these libraries have not been migrated to v15, CMR is failing to connect.

Workaround

Upgrade all repository tables/libraries to current build

This was done by using an eval license

To reproduce the issue:

1) create repository in v12.5 using studio enterprise

2) upgrade to 15.1 using DataArchitect enterprise

3) upgrade repository to v15.1

4) attempt to connect to repository via CMR

One of the errors reads:

ERROR Thread-1 2010/04/05 10:18:40 EDT com.sybase.cmr.infra.server.persistence.db.DbMetaPersistenceManagerImpl.createMetaClasses(DbMetaPersistenceManagerImpl.java:826) Exception occurred while loading metaclass(383:Object-Oriented Model)

ra_status output for

"REPLICATING Transitioning - Stopping

LogReader immediatly" message.

to get RepAgent license

information.

ERROR #1028 DSI EXEC(116(1) REL1502_cran2.master) - /dsiexec.c(513)

Message from server: Message: 7742, State 1, Severity 16 -- 'You must change your password using the sp_password system stored procedure before you can continue.

Linux 2.6.9-42.ELsmp i686/1/OPT/Thu Oct 15 16:15:54 2009

there are two problems here ...

after inserting 500 rows in a table ...

with the connection to the standbyDS.standbyDB suspended ...

*********************************************

isql -S<activeDS> -Usa -P -w2048 -D<activeDB>

declare @var int

select @var=1

while @var<= 500

begin

insert t01 values(@var, 'skip')

select @var=@var+1

end

go

quit

*********************************************

resume connection to standbyDS.standbyDB skip 500 transaction ...

1) failure to record all skipped xacts in rs_excepts* tables

2) failure to actually skip the xacts ..

it appears all 500 are skipped ... by the response to the ...

resume connection to standbyDS.standbyDB skip 500 transaction

****************************************************************

isql -S<rs> -Usa -P -w2048

1> resume connection to <standyDS>.<standyDB> skip 500 transaction

2> go

Connection to '<standyDS>.<standyDB>' is resumed.

1>

****************************************************************

but only 21 are recorded in the RSSD in the rs_excepts* tables ... ??? ...

and more surprising is 479 rows replicated ... !!! ... ??? ...

This is not possible with out current Users Management due the "Manage Users" rights can give all rights to his own User.

Currently, PowerDesigner only allows one DBMS user per repository definition to connect to the repository database.

Currently, the permissions are being maintained within the repository database only.

active at the same time, a mini-rollback for one

transaction is processed, the rollback operation

send to Replication Server can be 'skipped' as a

duplicate because the rollback operation's

location is too old.

to downgrade your Replication Agent instance from

version 15.5 back to version 15.2. Users wishing

to downgrade their Replication Agent instance will

need to make sure their target downgrade

Replication Agent is running 15.2 ESD #2 or later

before attempting to downgrade their Replication

Agent instance.

'%SYBASE%\REP-15_5\ASA11\scripts' are missing.

These scripts support, amongst other things, the

ability to unload a SQL Anywhere database which

is a critical step in upgrading an Embedded

RSSD.

of private copies of critical DLL files used by

Replication Server are stored in

'%SYBASE%\%SYBASE_REP%\bin'. For NT386 and

WINX64 RS 1550 GA, this set is incomplete which

can cause Replication Server to reference

incompatible DLL files that could cause

Replication Server to fail.

rs_create_repdef will create wrong

repdef for warmstandby,

if RepAgent has not ever been

started for replication.

"rs_init" fail with following error:

> Cannot read file '/dev/zvol/rdsk/sybase/rspe10_01'.

> Operating system returned: Invalid argument

installation will report in the file '${SYBASE}/log/RepServer_Suite.log'

a runtime exception in 'com.sybase.ia.common.SybaseDestination'.

Request:

improve the transactional aspect of the PD when deleting a version ie. break up the work into smaller transactions and keep track of the progress . This will ensure recovery or ability for PD to resume the delete of the version, if a failure occurs before the full logical delete of the version is complete

ra_dump command fails with exception: "Execution

failed because: <SQL execution failed.>" on

Microsoft SQL Server 2005.

Currently, the Repository Metamodel provides user and group information in a way that

- the user contains information about

- which group it is in

- which permission he has

- the group contains information about

- which users are member of it

- which groups it belongs to (parent group)

- which permissions it has

Customer would like to have another information added to the metamodel:

- a user or a group can be marked as functionally responsible for maintaining specific repository folders