PK78822: SYBASE SCRIPTS DO NOT WORK ON REMOTE SYBASE

Fixes are available

APAR status

Closed as program error.

Error description

Running WebSphere Application Serve Network Deployment with one
node federated.

1)Modified the auto.properties of cei-cvt.properties for
sybase db.
2)I have run the setup that creates cluster1 with server1 and
server2
3) Then the configsybase db command is run with all the
parameters and with create db set to false as we are running
using the remote sybase.
4)The sybase scripts are copied onto the sybase remote server

When i run cr_event_sybase.bat  it does not work and faile to
create db.
Erorr trace is:
{
tf1ansiansicpg1252deff0deflang1033{fonttbl
{f0fswissfcharset0 Arial;}}
{*generator Msftedit 5.41.15.1507;}
viewkind4uc1pardf0fs20 C:\Documents and
Settings\Administrator\Desktop\sybase>cr_event_sybase.bat
ceipar
rowndog 1 fvtdb05 sauserid=sa sapassword=par
Parameter Name                 Default     Memory Used Config
Valuepar
Run Value    Unit                 Typepar
------------------------------ ----------- -----------
------------par
------------ -------------------- ----------par
number of devices                       10         #30
25par
25 number               dynamicpar
par
(1 row affected)par
Configuration option changed. ASE need not be rebooted since
the option ispar
dynamic.par
Changing the value of 'number of devices' to '25' increases
the amount of memopar
par
ASE uses by 68 K.par
(return status = 0)par
Parameter Name                 Default     Memory Used Config
Valuepar
Run Value    Unit                 Typepar
------------------------------ ----------- -----------
------------par
------------ -------------------- ----------par
max memory                           39936      116736
58368par
58368 memory pages(2k)     dynamicpar
par
(1 row affected)par
Configuration option changed. ASE need not be rebooted since
the option ispar
dynamic.par
Resulting configuration value and memory use have not changed
from previouspar
values: new configuration value 58368, previous value
58368.par
(return status = 0)par
Msg 5123, Level 16, State 1:par
Server 'FVTDB05', Line 15:par
DISK INIT encountered an error while attempting to open/create
the physicalpar
file. Please consult the ASE error log (in the ASE boot
directory) for morepar
details.par
Msg 5123, Level 16, State 1:par
Server 'FVTDB05', Line 3:par
[...]
DISK INIT encountered an error while attempting to
open/create
the physicalpar
file. Please consult the ASE error log (in the ASE boot
directory) for morepar
details.par
Warning: Attempting to change database options for a temporary
database.par
Database options must be kept consistent across all temporary
databases.par
Database option 'select into/bulkcopy/pllsort' turned ON for
database 'tempdb'par
Running CHECKPOINT on database 'tempdb' for option 'selectpar
into/bulkcopy/pllsort' to take effect.par
(return status = 0)par
There is no disk named 'cei1_event_system'. Checking other
disk names.par
Msg 1802, Level 16, State 1:par
Server 'FVTDB05', Line 6:par
CREATE DATABASE failed. Some disk names listed in command were
not found. Checpar
that names exist and are spelled correctly before
re-runningpar
[...]
Database option 'ddl in tran' turned ON for database
'tempdb'.par
Running CHECKPOINT on database 'tempdb' for option 'ddl in
tran' to take effecpar
par
(return status = 0)par
Msg 911, Level 11, State 2:par
Server 'FVTDB05', Line 5:par
Attempt to locate entry in sysdatabases for database 'event1'
by name failed -par
no entry found under that name. Make sure that name is entered
properly.par
Msg 17590, Level 16, State 1:par
Server 'FVTDB05', Procedure 'sp_addsegment', Line 102:par
The specified database does not exist.par
(return status = 1)par
[...]
Msg 17590, Level 16, State 1:par
Server 'FVTDB05', Procedure 'sp_dropsegment', Line 104:par
The specified database does not exist.par
(return status = 1)par
(return status = 0)par
(return status = 0)par
Msg 17421, Level 16, State 1:par
Server 'FVTDB05', Procedure 'sp_dboption', Line 197:par
No such database -- run sp_helpdb to list databases.par
(return status = 1)par
[...]
The following services are dependent on the Sybase SQLServer _
FVTDB05 servicepar
Stopping the Sybase SQLServer _ FVTDB05 service will also stop
these services.par
par
Sybase MONServer _ FVTDB05_MSpar
par
Do you want to continue this operation? (Y/N) [N]:par
par
C:\Documents and
Settings\Administrator\Desktop\sybase>parpar
par
}

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All WebSphere Application Server V6.1 and   *
*                  V7.0 Common Event Infrastructure (CEI)      *
*                  users who perform the configuration with a  *
*                  Sybase database located remotely.           *
****************************************************************
* PROBLEM DESCRIPTION: The common scenario for configuring     *
*                      the Common Event Infrastructure with    *
*                      a remote Sybase database includes the   *
*                      step for the database creation via      *
*                      generated scripts that contain the      *
*                      specific DDL/DML statements. When       *
*                      you perform the manual process of       *
*                      database creation with a Sybase         *
*                      database located remotely the           *
*                      process fails due to the fact that      *
*                      the devices creation statements were    *
*                      generated erroneously (in particular,   *
*                      the locations for the devices does      *
*                      not point to valid directories).        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Typically when you intend to perform the Common Event
Infrastructure with a remote Sybase database the configuration
process consists of issuing the specific Sybase configuration
AdminTask with createDB parameter set to false. The result of
this process is the automatic configuration of Common Event
Infrastructure platform except for the creation of the
database and its objects. This is due to the fact that
remote automatic database processing cannot be performed. That
is, in order to complete the configuration process you have to
copy the generated scripts containing the DDL/DML statements
to the remote database server and run them locally. When
cr_event_sybase.bat is run the database creation process fails.
This is due to the fact that the scripts generation process
performs a validation of the issued Sybase installation
location on the local computer. The validation operation is
not performed correctly and this leads to an incorrect
generation at the Sybase devices scripts level.

Problem conclusion

The verification process for the issued Sybase installation
directory has been reviewed and changed in order to skip this
in case the database is not automatically created. That is the
typical case when the Sybase server is located remotely and
the validation for the existence of the Sybase installation
folder should not be performed anymore on the local computer.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.25 and 7.0.0.3.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

You have the option to manually check the content of the
cr_db_devices.syb and correct the location for the devices
according to the local directory structure.

Comments

APAR Information

APAR number
PK78822
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-01-16
Closed date
2009-01-28
Last modified date
2009-02-16

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK78822: SYBASE SCRIPTS DO NOT WORK ON REMOTE SYBASE

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?