I can't find any information about CCMS monitoring of ASE DB.

Which possibilities exists to monitor an ASE with autoreaction or when it is possible?

(maybe exists a guide for this issue?!)

BR Heiko Cudok

Dear Sybase Experts,

I am performing Homogeneous System copy using backup/restore method.I have taken QA system backup ie dump files and trying to build on Sandbox system for testing purpose.Everything went fine and was able to load the dump but stuck at one of the point and throwing me error

ERROR      [cinstallercallbackimpl.cpp:228]

CJS-00030  Assertion failed: Execution of SQL script reports an unexpected error.

When I checked the sapinst_dev log I found the below error but not able to fix it and not aware to proceed further

1> use SID

1> EXEC sp_changedbowner sapsa

Msg 17362, Level 16, State 1:

Server 'SID', Procedure 'sp_changedbowner', Line 181:

The proposed new db owner already is a user in the database or owns the database.

(return status = 1)

I am sure these may be small changes that have to be made by changing the db owner and Im not exactly sure how to perform it.

Note:I am Using the Windows environment with Sybase ase database and SWPM tool to perform.

Appreciate your suggestions

Thanks

Asim

Hi All

I have an ASE db that is in a RECOVERY state.

This the last communication in the log: Started filling free space info for database 'BWP'

Does anyone know what this means?

There is a SAP BW running on ASE 15.7.

I am an SAP consultant working onsite at a client and the environment is down due to the DB being in this state.

Any ideas?

00:0002:00000:00014:2014/07/03 10:27:18.04 server  Recovering database 'BWP'.

00:0002:00000:00014:2014/07/03 10:27:18.05 server  Started estimating recovery log boundaries for database 'BWP'.

00:0002:00000:00014:2014/07/03 10:27:18.07 server  Database 'BWP', checkpoint=(249429512, 203), first=(249429512, 203), last=(249429513, 46).

00:0002:00000:00014:2014/07/03 10:27:18.07 server  Completed estimating recovery log boundaries for database 'BWP'.

00:0002:00000:00014:2014/07/03 10:27:18.07 server  Started ANALYSIS pass for database 'BWP'.

00:0002:00000:00014:2014/07/03 10:27:18.07 server  Completed ANALYSIS pass for database 'BWP'.

00:0002:00000:00014:2014/07/03 10:27:18.07 server  Log contains all committed transactions until 2014/07/03 10:19:12.65 for database BWP.

00:0002:00000:00014:2014/07/03 10:27:18.07 server  Started REDO pass for database 'BWP'. The total number of log records to process is 81.

00:0002:00000:00014:2014/07/03 10:27:18.14 server  Completed REDO pass for database 'BWP'.

00:0002:00000:00014:2014/07/03 10:27:18.14 server  Timestamp for database 'BWP' is (0x0004, 0xd609797b).

00:0002:00000:00014:2014/07/03 10:27:18.14 server  Recovery of database 'BWP' will undo incomplete nested top actions.

00:0002:00000:00014:2014/07/03 10:27:18.14 server  Started recovery checkpoint for database 'BWP'.

00:0002:00000:00014:2014/07/03 10:27:18.14 server  Completed recovery checkpoint for database 'BWP'.

00:0002:00000:00014:2014/07/03 10:27:18.14 server  Started filling free space info for database 'BWP'.

ASE VERSION:

Adaptive Server Enterprise/15.7/EBF 22779 SMP SP122 /P/x86_64/Enterprise Linux/ase157sp12x/3662/64-bit/FBO/Sat Apr 19 05:48:19 2014

Any suggestions on what to do?

J

Where is PC Client for ASE?

Starting with SAP ASE 16.0 there is NO longer a PC -Client for Windows.

Instead you will get the SAP SDK (Software Devlopers Kit) for ASE and then pick the Windows platform.
(ref Ryan Hansen Helpful Answer in the thread to get the SDK for ASE: Where are the Sybase ASE 15.7 client downloads for 64bit?)

Products dropped:

ASE OLE DB driver is no longer part of the 16.0 series
ADO.NET 2.0 driver

Sybase Central

Changes in directory structure:

$sybase\OCS-15_0 is now $sybase\OCS-16_0

jConnect-7_0 is now jConnect-16_0

DBISQL (Interactive SQL) was added to the SDK

Products included SDK 16 for Windows

ADO.NET 3.5 driver  for both 32/64 bit

ADO.Net 4.x driver for both 32/64 bit

ODBC driver for both 32/64 bit

Perl module only for x64 bit and samples(certified with Perl 5.14.0 and 5.14.1)

PHP module only for x64 bit and samples(certified with PHP 5.3.6)

Python module on for x64 bit and samples(certified with Python 2.6, 2.7 and 3.1)

Ctlib binaries/samples

Dblib binaries/samples

Embedded SQL/C binaries/samples

Embeded SQL/Cobol binaries/samples

jConnect 16 with jconn4.jar binaries/samples

If you still need PC-Client.
You need to look under the Adaptive Server Enterprise 15.7 or older install.

Follow this thread: http://scn.sap.com/thread/3565945

Hi Experts,

We have two dailog instances and one PRD server.I configured logon load balance in SMLG transaction code.Even though all the users are logged in to PRD server only.No users in the dailog instances.Please help in this.

Thanks&Regards,

Patan Thavaheer.

Hi Experts,

We need to modify the history retention in the DBA Cockpit for database growth. Could you specify which Data Collector is responsible for this data?

Thank you!

Best regards

Janos

Configuring Automatic Database Space Expansion in SAP Adaptive Server Enterprise

Author:  Markus Ohly, SAP SE
Classification: Public
Status: Published to SCN / V1.0 / July 9, 2014

1. Introduction

This white paper introduces system administrators to the automatic database expansion feature in SAP Adaptive Server Enterprise (SAP ASE). Here we will focus on deployments of SAP Business Suite applications running on SAP ASE.

With automatic database expansion activated, administrators can further reduce the time needed for administration tasks. More importantly, interruptions to business users - such as an ASE error SQL1105 caused by missing resources, for example -  can be avoided because the database server can automatically obtain the space resources needed for continuous operation.

The following sections explain which software component levels are needed for running automated database expansion and show how to set them up during installation or later on.  In addition, you will find recommendations for threshold and expansion sizes.

2. Version Requirements

Use SAP Software Provisioning Manager 1.0 SP4 or newer to configure automatic database expansion during installation.

Update SAP_BASIS to support package releases listed in SAP Note 1814258 in order to manage automatic database expansion using the DBA Cockpit.  SAP recommends implementing the most recent DBA Cockpit correction collections that are listed in the section "Important SAP Notes".

Update SAP Adaptive Server Enterprise 15.7 to SP51, or higher as recommended in SAP Note 1554717.

3. Configuring Automatic Database Expansion with SWPM During System Installation

When starting a new system configuration in the installer, choose parameter mode "Custom" rather than "Typical":

Fill in the fields as required in the subsequent screens until you reach following screen:

Choose "Configure database for automatic expansion" to setup automatic expansion; the next screens will ask you to specify the configuration values for automatic database expansion that will be used during the installation of the database server for the SAP system.

In the first screen the non-expandable devices can be configured. Note that the data devices for the SID database are not listed here and should not be added; these will appear in the next screen.

Click  "Next". The SAP installer will  proceed to the configuration of the parameters for the expansion of the <SID> database and the underlying devices. 

Set a value for the Growby size parameter; the database server will perform expansion of the <SID> database by this amount of space each time the free space in this database falls below the free space threshold.

Set a Free space threshold value of at least 1GB. This parameter enables the expansion process to start in the background, before actually running out of space. 

You can add further database devices using the Add button to distribute the data onto separate file systems. The Growby size may be set individually for each device; SAP recommends that the Growby size be equal for all devices.

The Growby size for each device should be less than or equal to the Growby size of the database, and the database Growby size should be an integral factor of the device Growby size(s). SAP recommends having each device grow by equal sizes. The file systems must provide enough free space to perform device expansion when needed.

Complete the following screens and execute the installation.

4. Configuring Automatic Database Expansion in Existing SAP Systems Running on SAP ASE

For systems configured with the installer prior to SWPM 1.0 SP02, you have to install the database scripts needed for automatic expansion. DBA Cockpit displays the following error message in case this is necessary:

Instructions for installing  the required components are provided in the appendix: install dbextend script.

5. Setup with DBA Cockpit

The following picture shows the DBA Cockpit view of an SAP system without automatic database expansion. Note that all indicators in the column Auto Expansion are gray:

To enable automatic database expansion for the SID database, click on the corresponding row so that the segments are displayed; then select the row for the "default" segment:

Choose the "Change" button:

Click the check button to perform a consistency check of the values entered. Click the save button to permanently set the entered values:

6. Recommendations

SAP recommends setting the following expansion policies:

• For the SID database, set the expansion size to 1G and the free space threshold to 1G
• For the saptools database, set the expansion size to 128M and the free space threshold to 256M

SAP strongly recommends against automatically expanding the log segment of any database.  Log segment expansions increase the impact from run-away transactions and may cause lengthy recovery times during which the system is unavailable.

7. Trace Records of Automatic Database Expansion

Whenever automatic expansion is performed, the actions will be logged in the SAP ASE errorlog. SAP ASE can perform two steps: first, if required, one of the expandable devices will increase in size by the given amount. Secondly, the database itself will be expanded by the predefined amount of space.

Example:

00:0002:00000:00039:2014/03/24 23:14:18.96 server  background task message: Threshold action procedure 'sp_dbxt_extend_db' fired in db 'IDS' on segment 'default'. Space left: 131072 logical pages ('2048M').
00:0002:00000:00039:2014/03/24 23:14:19.10 server  background task message: DISK RESIZE name = 'IDS_data_002', size = '2048.0M' -- Db: IDS Segment: default
00:0005:00000:00000:2014/03/24 23:14:19.15 kernel  Performing space allocation for device '/sybase/IDS/sapdata_2/IDS_data_002.dat' (2.00 Gb).  This may take some time.
00:0002:00000:00039:2014/03/24 23:14:39.81 kernel  Finished initialization.
00:0002:00000:00039:2014/03/24 23:14:39.95 server  background task message: sp_dbxt_do_resize_dev: Device IDS_data_002 of size 30720M resized by 2048M to a total size of 32768M.
00:0002:00000:00039:2014/03/24 23:14:39.95 server  background task message: ALTER DATABASE IDS on IDS_data_002 = '2048.0M' -- Segment: default
00:0002:00000:00039:2014/03/24 23:14:39.96 server  Extending database by 131072 pages (2048.0 megabytes) on disk IDS_data_002
00:0002:00000:00039:2014/03/24 23:14:41.72 server  Processed 52 allocation unit(s) out of 512 units (allocation page 4403968). 10% completed.
...
00:0002:00000:00039:2014/03/24 23:14:56.92 server  Processed 512 allocation unit(s) out of 512 units (allocation page 4521728). 100% completed.
00:0002:00000:00039:2014/03/24 23:14:57.28 server  background task message: Database 'IDS' was altered by total size '2048M' for segment 'default'.

If the maximum device size set is reached during configuration or administration, the following traces are written:

00:0002:00000:00030:2014/03/25 06:25:12.29 server  background task message: Threshold action procedure 'sp_dbxt_extend_db' fired in db 'IDS' on segment 'default'. Space left: 131072 logical pages ('2048M').
00:0002:00000:00030:2014/03/25 06:25:12.50 server  background task message: Database 'IDS' was altered by total size '0M' for segment 'default'.

Note that there is still some free space available (2048 MB) in the database so that transaction processing can still continue for some time; however, no further automatic expansion can happen anymore. Without administrative action it is possible that all the free space gets used and transaction processing stops with error messages. Ultimately, the users will see RABAX errors and the database server will indicate that no more free space is available

00:0002:00000:00036:2014/03/25 06:29:12.65 server  Error: 1105, Severity: 17, State: 2
00:0002:00000:00036:2014/03/25 06:29:12.68 server  Can't allocate space for object 'VRSX4' in database 'IDS' because 'default' segment is full/has no free extents. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE to increase the size of the segment.

The DBA Cockpit indicates that the maximum size of a database device has been reached with an alert:

8 Further reading

SAP Adaptive Server Enterprise 15.7 ESD #2, System Administration Guide: Volume 2, Chapter 16: Expanding Databases Automatically
http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc31644.1570/html/sag2/CEGDAFBH.htm

Getting started with SAP Business Suite on SAP ASE: http://scn.sap.com/docs/DOC-29524

8.1 Important SAP Notes

1554717 - SYB: Planning information for SAP on ASE
1814258 - SYB: DBA Cockpit Release Notes 7.02 SP14, 7.30 SP10, 7.31 SP9, 7.40 SP4
1558958 - SYB: DBA Cockpit Correction Collection SAP Basis 7.02 / 7.30
1619967 - SYB: DBA Cockpit Correction Collection SAP Basis 7.31
1882376 - SYB: DBA Cockpit Correction Collection SAP Basis 7.40
1815695 - SYB: Automatic database expansion for SAP Sybase ASE
1602547 - SYB: Current syb_update_db script versions
1883967 - ASE sp_dbextend does not observe default device growby limits

Appendix A: install dbextend script

A.1 Linux and UNIX:

Connect and/or login as user syb<sid>

% cd ${SYBASE}
% . SYBASE.sh
% isql -Usapsso -S<SID> -X
Password:
1> sp_locklogin "sa", "unlock"
2> go
Account unlocked.
(return status = 0)
1> quit
% isql -Usa -S<SID> -X -i${SYBASE}/${SYBASE_ASE}/scripts/installdbextend
Password:
% isql -Usa -S<SID> -X
Password:
1> if object_id('sybsystemprocs..sp_dbextend') > 0
2> begin
3>   exec sp_dbextend 'modify', 'device', 'default', 'growby', '0'
4>   exec sp_dbextend 'modify', 'database', 'default', null, 'growby', '0'
5>   exec sp_dbextend 'disable', 'database', 'default'
6> end
7> go
(return status = 0)
(return status = 0)
(return status = 0)
1> quit
% isql -Usapsso -S<SID> -X
Password:
1> sp_locklogin "sa", "lock"
2> go
Account locked.
(return status = 0)
1> quit

A.2 Windows:

Connect to the DB host as user syb<SID>, open a DOS command window and type in the following commands:

C:\Windows>cd /d %SYBASE%

G:\sybase\SID>SYBASE.bat
G:\sybase\SID>isql -Usapsso -S<SID> -X
Password:
1> sp_locklogin "sa", "unlock"
2> go
Account unlocked.
(return status = 0)
1> quit

G:\sybase\SID>isql -Usa -S<SID> -X -i %SYBASE%\%SYBASE_ASE%\scripts\installdbextend
Password:
G:\sybase\SID>isql -Usa -S<SID> -X
Password:
1> if object_id('sybsystemprocs..sp_dbextend') > 0
2> begin
3>   exec sp_dbextend 'modify', 'device', 'default', 'growby', '0'
4>   exec sp_dbextend 'modify', 'database', 'default', null, 'growby', '0'
5>   exec sp_dbextend 'disable', 'database', 'default'
6> end
7> go
(return status = 0)
(return status = 0)
(return status = 0)
1> quit
G:\sybase\SID> isql -Usapsso -S<SID> -X
Password:
1> sp_locklogin "sa", "lock"
2> go
Account locked.
(return status = 0)
1> quit

Configuring Automatic Database Space Expansion in SAP Adaptive Server Enterprise

This white paper introduces system administrators to the automatic database expansion feature in SAP Adaptive Server Enterprise. The author will focus on deployments of SAP Business Suite applications running on SAP ASE. With automatic database expansion activated, administrators can further reduce the time needed for administration tasks. More importantly, interruptions to business users can be avoided because the database server can automatically obtain the space resources needed for continuous operation.

Important Information

An issue has been identified that can potentially cause incorrect results in an SAP Business Warehouse system running on SAP Adaptive Server Enterprise.
The problem has been observed whenever the optimization goal 'allrows_dss' or another optimization goal that includes optcriteria 'advanced_aggregation'is used for an SQL statement. This is typically the case for SAP BW systems. SAP ERP systems running on ASE are not affected. In SAP ERP systems optimization goal 'allrows_mix' has been configured.

Details and corrections are available in SAP Note 2026328- SYB: Incorrect results with SUM aggregation on decimal fields.We strongly recommend to implement the corrections in SAP BW as soon as possible.

Getting Started with SAP Applications Using SAP Adaptive Server Enterprise

The aim of this document is to help you get started with the SAP Adaptive Server Enterprise (ASE) database that is run with SAP applications.

Continuous Availability Solutions for SAP Adaptive Server Enterprise

Over the past years, SAP ASE has supported a number of high availability solutions that work as a complement to hardware solutions in providing reduced downtime and recovery effort for applications. ASE HADR in SAP ASE 16 will enhance the offerings, bringing the same transparent client failover, zero data loss, and ease-of-use capability that cluster systems enjoy with ASE installations that are long distances apart.

On the Road to an Enterprise Cloud

Customer demands for support of virtualization are rapidly growing. SAP offers support for running its applications in virtualized cloud environments. You can start your projects and can bring the innovations from SAP into production in a matter of weeks instead of months, with complete flexibility of deployment choice.
SAP Landscape Virtualization Management (LVM) is available for SAP Business Suite on SAP Adaptive Server Enterprise.

For more information, read thisarticle, and SAP Notes 1630050 and 1492000.

DBA Cockpit: Automatic Table Maintenance for SAP ASE

Maintaining tables, indexes and data partitions is crucial for productive database systems. Continuous insertion, update and deletion of data induces fragmentation, bad cluster ratios and inaccurate optimizer statistics. The article shows how the DBA Cockpit and its automatic table maintenance for SAP ASE ensures good cluster ratios on tables and indexes, frees up unused space and ensures accurate optimizer statistics.

General Availability of SAP Adaptive Server Enterprise

SAP Business Suite on ASE is available for SAP Business Suite 7i2010, 7i2011, and 7i2013.
For more information, refer to SAP Note 1554717.

Hi All

I have an ASE 15.7 dataserver running BW on Linux that (according to the network admin) is displaying very high memory usage.
This is causing memory swap to kick in. I can see dataserver is using on avg. 86.8% of memory and all the BWP_01_DIA_* is using a bit of memory as well. eg. BWP_01_DIA_W5, BWP_01_BTC_W32,

occasionally it spikes to over 100%, thus swap kicking in.

Is this normal behaviour? How does one check what is consuming the memory?

What %MEM as displayed in "top" on Linux is considered normal?

The environment details are:

Adaptive Server Enterprise/15.7/EBF 22779 SMP SP122 /P/x86_64/Enterprise Linux/ase157sp12x/3662/64-bit/FBO/Sat Apr 19 05:48:19 2014                      

top output:

PID       USER      PR  NI  VIRT  RES  SHR   S   %CPU %MEM  TIME+      COMMAND

55009   sybbwp    20   0   172g  163g  163g   S   209      86.2      14939:46  dataserver

54967   bwpadm   20   0   138g  201m 154m S    9          0.1        0:01.24     BWP_01_DIA_W12

3775     root          20   0   9412  1012   248    R    1         0.0        58:02.31   top

Hi,

I installed SAP Netweaver 7.40 & Enterprise Portal ( no ABAP installation exists on this installation )  on Sybase ASE 16.0.00.00.. I would like to use Sybase Replication Server for HADR..

1. is it possible to use SRS for SAP Netweaver

2. if it is possible which version of SRS should be suitable on SAP marketplace

Regards,

Oguzhan

Hi,

I am trying to setup an IDES Server and downloaded the latest packages from market place.

Operating System: SLES 11 SP3, in SAP flavour as it is provided by Novell.

There is enough space on disks as per Note 2012989 and the Installation Guide.

This is my first Sybase SAP-Installation.

The error appears in phase "Setup Backup Server".

bsrv,log:

Building Backup Server 'SIS_BS':

Writing entry into directory services...

Directory services entry complete.

Writing RUN_SIS_BS file...

RUN_SIS_BS file complete.

Starting server...

Unable to boot server 'SIS_BS'. 

Task failed

Server 'SIS_BS' was not created.

And from sapinst_dev.log:

CJS-00030  Assertion failed: Unable to set up backup server. Refer to trace file sapinst_dev.log for further information.

Member function 'Installer.abortInstallation()' has thrown ESAPinstException. Converting to JavaScript exception EJS::Exception.

Function setMessageIdOfExceptionMessage: modlib.jslib.caughtException

MUT-03025  Caught ESAPinstException in module call: .

Member function 'Installer.invokeModuleCall() has thrown unknown exception. Rethrowing.

Thanks for looking and any hints welcome.

Sven

Guys,

(Ryan & Dawn),

What are possible solutions to:

ASEOLEDB 30012 Disconnect between a PC Client and a unix machine?

Cory

Hi,

I am new to Sybase database. I have just installed ECC6 EHP5 on Sybase database. I do not know how to backup and restore the database. Can anyone please guide me.

Regards

Ivan

Dear Experts,

I am facing one issue.Actually dailog work process is taking more time to execute the transaction.If the simple transaction code also it is taking more time to execute.Other work process are free only.Please five me suggestions on this.Thanks in advance.

Regards,

Patan Thavaheer.

Hi, 

I have installed ECC 6.0 ehp6 with SYBASE 15.7  DEV/QA and PRD systems and they are working fine , now requirement is need to restore QA system using PRD backup . 

I would like to do restore quality database with production data system. Kindly help me the Presteps /procedure /post steps regarding this!

Thank you.

Thanks

chenna

Hi,

I have installed ECC 6.0 ehp6 with SYBASE 15.7  DEV/QA and PRD systems and they are working fine , now requirement is need to restore QA system using PRD backup . 

I would like to do restore quality database with production data system. Kindly help me the procedure regarding this!

Thanks

chenna

Dear Experts,

Actually we are having one PRD server and two dailog instances.If we schedule the MRP background jobs, the jobs are running in dailog instances.And some times they are active for long time and then we manually cancelling the jobs.Please give suggestions to run the jobs in PRD server only not in dailog instances.

Thanks&Regards,

Patan Thavaheer.

Hi ,

         We installed EHP7 on ASE 15.0& Linux, After that we stopped the server and while starting it is not coming Up it is saying system crash, can you please suggest me.

we don't have backup, it is newly installed system.

Startdb.log:

------------------------------ Tue Jul 22 13:32:24 IST 2014

LOGFILE FOR STARTING SYBASE ASE

starting database XXX ...

------------------------------ Tue Jul 22 13:32:25 IST 2014

checking required environment variables

------------------------------ Tue Jul 22 13:32:25 IST 2014

check if Sybase ASE processes are running

ASE instance not available

*** ERROR:ASE instance possibly left running when system

    went down(system crash?).

    Notify Database Administrator.

------------------------------ Tue Jul 22 13:32:25 IST 2014

check if Sybase Backupserver is running

Backupserver instance not available

Database not available

parse level 0: identified message 'Database 'master' is now online.'

parse level 1: identified message 'Database 'tempdb' is now online.'

parse level 2: identified message 'Database 'sybsystemprocs' is now online.'

------------------------------ Tue Jul 22 13:48:32 IST 2014

/usr/sap/XXX/SYS/exe/run/startdb was killed or interrupted. Terminating.

regards,

Rajshekar

 

Hi experts,

I reveived the error: Execution of the command "/bin/csh -c "source /home/qasadm/.cshrc; env"" finished with status TST_ERROR, in sybase System Copy.

I checked all permissions and passwords of the users, but it is not working.

Please i need your help in looking for this solution.

Thank you!

Rene Antunes