SAP ASE 15.7 installation error
Sybase DR setup using log shipping
Hello Experts,
Could you please explain me steps to configure the log shipping procedure for sybase in details.
i know there is a standard SAP note 1650511 which contains scripts as well.
My present OS is RHEL 6.2 and sybase 15.7
Present we are maintaining the DR server within LAN for a distance of 2 km at different location.Later after one month we will be shifting it to different geographical location.
Also i have a few questions in my mind,
1.what happens when there is network disconnection
for about 20 hours (or) about 3 days with DR server (standby system)?
will the transaction logs will trigger in DR ?? (or) else any manual process need to be follow??
2.what are the major pre-requisites to be taken care before the DR drill?
Like in a HA we need to maintain all the shared disks and file size should equal in both nodes ?
Is it similar for DR setup?
3.In future after one year we want to use standby server as a primary server as
hardware is good enough in DR server compared to Primary?If we change then what will be the procedure?
4.I m taking daily full on line database backup but i have taken transaction log after one month and now
the SAP system is crash.I have build new system and restore the latest database dump and my question is
whether i can restore the transaction log backup of 30 days because already full on line database backup is applied,if it is restore
from what sequence it will apply the transaction log backup???
Thanks in Advance.
Adaptive Server requires encryption of the login password on the network
Hi experts,
I have installed a distributed configuration of BO BI 4.1 SP5 on Linux RH 6.5 with Sybase ASE 15.7 SP 131 :
SAP ASE 15.7 SP131 on one server & CMS on an other server.
Everything works well.
Now, I would like to activate "net password encryption reqd" on my Sybase server.
But when this parameter is activated, CMS server doesn't start anymore :
more error_boe_cmsd6400.log
33007 SAP BusinessObjects BI platform CMS: Unable to connect to the CMS system database ""<SID>"". Reason: Adaptive Server requires encryption of
the login password on the network.
35101 The root server reported an error Initialization Failure. (Reason: SAP BusinessObjects BI platform CMS: Unable to connect to the CMS syst
em database ""<SID>"". Reason: Adaptive Server requires encryption of the login password on the network. SAP BusinessObjects BI platform CMS: Unabl
e to connect to the CMS system database ""<SID>"". Reason: Adaptive Server requires encryption of the login password on the network. CDatabase::Op
en failure. ).
Can someone help me?
What kind of connection mechanism is used by CMS server to access CMS DB Repository?
Regards
TIME_OUT when try to schedule DB backup(database dump)
Hi experts,
I want to schedule database dump.
In summary tab, when I click execute, it will loading until TIME_OUT error occur.
https://drive.google.com/folderview?id=0B62cNgHiqy9Ia2E3U0tIeGQ5RHc&usp=sharing
Please help.
Thank you.
Regards,
Fadzly Iqbal
SM12 lock Issue-Not getting released automatically
Hello Friends
One of my customer facing SM12 lock issue which occurs only in night time.During Day hours issue does not counter us.Once its get locked he has to delete the lock entry in SM12 and repeat. Below is the inputs from customer.
- A user logs into the system for a transaction
- A Dialogue opens
- The moment the dialog opens the relevant database table gets locked
- there are 2 option for the user either he updates or he cancels the dialogue
- If he Cancels the database lock should get release
- If he updates then after updation the data base lock should get released
What were the areas where we have been finding difficulty:
In case 5 when user comes out wirhout updating the data base lock doesn't get released, so we have to release it through SM12
In case 6 what was happening the updation happens in two step update 1 and update 2. So the same was failing either in updation 1 or updation 2 and therefore the data was staying locked. In this case we have to either using SM13 update the record and in cae of error delete the record and in such case the data base lock would get released automatically and we were not required to use SM12.
What appears to have been solved?
Since last 5 days there hasn't been a single case were any updation has failed.
What is still pending?
Case 5, i.e. when user cancels a transaction or dialogue and comes out of a transaction and again re-enters for a new record the system says data locked by the same user....In such case we manually using SM12 have to delete the lock.
Case 6 many times most update the database lock is not geting released and when the user logs in again and want to work in the same sales order he gets a message that the document is locked. In such case when we see the SM12 log we find the old set and new set both as locked. So when we delete the lock of the old set the lock of new set automatically clears and therefore the log gets cleared.
Does the problem have a pattern?
The problem primarily occurs after 9 PM at night and happens till 8.00 AM of next morning and doesn't appear in day time when the system is used by at least 60 concurrent users.
The problem occurs with VL01N transaction mainly and rarely with MIGO transaction. The problem doesn't occur with ZGATEPASS_In AND ZWEIGHBRIDGE. These transaction occurs anything between 50 -100 times during the period mentioned.
The problem of locking occurs once or twice in a sequence of entry i.e. if 10 vehicles enter for delivery (VL01N) it will get locked for 2 vehicles and then 8 vehicles will go without any problem again when the next sequence starts it may happen with the first one or with some subsequent ones and then it stays fine.
With the details shared I would like to mention that though it may appear the problem partly is solved
Below is the SM21 log entry.
10.05.2016 | 22:29:01 | prod21_EXP_00 | DIA | 003 | 600 | XXXXXXXX | @5C\Qvery high priority@ | GEO | Lock entry deleted manually: LIKP E |
10.05.2016 | 22:29:01 | prod21_EXP_00 | DIA | 003 | 600 | XXXXXXXX | @5C\Qvery high priority@ | GEO | Lock entry deleted manually: MARC E |
10.05.2016 | 22:29:01 | prod21_EXP_00 | DIA | 003 | 600 | XXXXXXXX | @5C\Qvery high priority@ | GEO | Lock entry deleted manually: VBAK E |
10.05.2016 | 22:32:38 | prod21_EXP_00 | DIA | 002 | 600 | XXXXXXXX | @5C\Qvery high priority@ | GEO | Lock entry deleted manually: LIKP E |
10.05.2016 | 22:32:51 | prod21_EXP_00 | DIA | 001 | 600 | XXXXXXXX | @5C\Qvery high priority@ | GEO | Lock entry deleted manually: MARC E |
10.05.2016 | 22:32:51 | prod21_EXP_00 | DIA | 001 | 600 | XXXXXXXX | @5C\Qvery high priority@ | GEO | Lock entry deleted manually: VBAK E |
Kindly Provide us the Inputs from your end where issue is pointing so that we can resolve quickly.
Regards
Pankaj
SAP SYBASE DR SETUP
Hello Friends,
We are looking for setup SAP SYBASE DR SETUP for one of our Customer.Kindly please share the inputs or guide if anyone have.
Current Customer OS :RHEL AND DB: SYBASE 15.7.Please correct me if i am wrong, through some search i had prepared steps below to start the activity.
1.On standby - Install SAP and Sybase database with same SID and system numbers (single host)
Post Installation: Activites:(This Post installation will perform on both Primary and Secondary Server if am not wrong)
1.Adapt the user environment for <sapsid>adm: Refer Note:1891560
2.Apply the latest version for the SAP ASE database available at http://support.sap.com/swdc:
3..Apply the latest version for the SAP Replication Server available at http://support.sap.com/swdc.
2.Update Sybase patch on secondary site to match that of primary database (SP 110 or above)
3.Install Replication server 15.7.1 SP 111 or above on both primary and standby servers.
4.Configure DR agents for replication between both sites.
5.Backup primary database and restore it on standby site
6.Start the database on standby site in recovery mode.
7.Monitor log shipping between both sites and plan for DR drill.
8. SAP NOTES: 1891560 - Disaster Recovery Setup with SAP Replication Server
Regards
Pankaj
SAP data collection framework - owner change
Hi,
in the data collection framework there is an owner assigned to all data collectors. In general the owner is the SID system itself.
If another system (i.e. solman) is connected to the system, the owner of the data collector changes to that system.
The data collection does not work any longer and creates a lot of errors.
I can change back the owner, but it changes immediately to the connected system.
Why does the data collector not work with the "foreign" owner? And why does the owner change at all?
Best regards
Arne
How to list the sizes of all tables (data and index seperately) ?
Hello,
I want to list the sizes of all tables (at least top 1000), data size and index size in seperate columns,
On DBACOCKPIT I can only display Top 500 and cannot display data and index size on the same list.
Index sizes come with single table analysis.
Is there an SQL statement that I can run on SQL Command line for this list?
Can you help, please?
Regards,
Yuksel AKCINAR
Queries on DR log shipping Process???
Hi All,
I have a few queries regarding the DR drill, request you to provide your valuable views on my queries?
1.For suppose we have done with log shipping and disconnected the DR server for 3 days ?How can we get back the DR server with same stage as previous? Is there any procedure to be follow?
2.Due to network fluctuation there is a continuous disconnection with DR ?What will be the situation? How can we recovery the transaction log with continuous fluctuation?
3.Assume we want to change the existing PRD server as DR and DR server as PRD later after few months? What is the procedure to be follow?
4.How much bandwidth is needed for DR as per the standard SAP methodology? And like HA do we need to maintain any specific pre-requisites for DR?
5.Regarding the backup, assume that we are not taking transaction logs backup daily but at the end of one month I,e. (30 days ) it filled with size of 30gb and usually we are taking full online backup. Now the system is crashed and we had performed the restore of online backup and then transaction of 30 days of size 30 gb? Will there is any conflict on applying transaction logs? Since already full online backup is applied but only a few transaction in the transaction logs is needed?
Regards,
Vivek Raj
Sybase WSB setup on ASE 16.0
downloaded the free copy of ASE 16 available at SAP site and I was testing warm standby setup on Linux with replication server 15.7.
- Installed sybase server sby01 using ASE 16.0 and create database db01
- Installed second sybase server syb02 using ASE 16.0 and create database db01
- At this point no other ASE 16.0 options is enabled i.e HADR mode is -1 and not enabled.
- Installed reserver rs01
- Added db01 database on syb01 as active in rs01 repserver : Successful
Now while adding db01 on syb02 as 'standby' it give error message
"WARNING: 'Create failed because Log transfer for database syb02.db01 is off'"
While i tried the setup on ASE 15.7 and I have no problem creating WSB setup. Seems HADR is somehow preventing database to be added as standby though it is not even enabled. Any clues where to look at, I checked there are no connections for syb02 and do not see any reference in rssd tables for syb02.
This is just test and want to know why I cannot setup WSB using ASE 16.0 free developer edition where as it works for free ASE 15.7 developer edition.
Performance issue during Alter table on a huge table having many indexes.
You can face the performance issue while running alter table on a very huge table having many indexes created.
for example : alter table takes around 38 hours for a very large table which has around 538 columns and 15 nonclustered indexes.
The table size is approx 600 GB having 7.5 millions of rows .
The reason for the performance issue is because the indexes are created serially.
To fix this performance issue, Please follow the below steps :
1. drop the indexes,
2. run the alter table,
3. recreate the indexes in parallel
Hope this will be helpful.
Memory Management - How to check usage?
Hello,
according to ASE documentation the parameter "total physical memory" is the used memory at the moment.
And the "total logical memory" is the configured memory at the moment.
We have one DB, where logical memory is lower than physical memory. How can this happen?
And total physical is exactly the value of max memory, does it mean that memory is used to the limit at the moment?
Kind regards
How to Monitor the Error Log in Sybase ASE
Tool for automatically checking the ASE errorlog
By Rob Verschoor
How to Monitor the Error Log
By Infocenter
upgrade_bs_rdbms.bat execution during the Sybase Upgrade from 15.7 to 16.0
Hello,
During the Upgrade of Sybase ASE from 15.7 to 16.0.
Now we had run the
1.setup console.. we did that from ASE_Suite we found 0 errors and 0 fatal errors .
according to the note 2162735
2.the next step is to run the batch file --> Upgrade_bs_rdbms.bat.When I have run this it has asked for sa password --> Windows User & password --> next it has prompt for ""master device path of ASE.""
Please help me which is the exact path of Master Device.
Thanks in advance.
DBA Cockpit ATM
Hi Friends,
Please need details on ATM DBA Cockpit for sybase and ATM step by step configuration.
Regards,
Akshay
Update ASE using saphostctrl
Hi all,
I am trying to update SAP ASE 16.00.01 to 16.00.02 on Windows 2012 R2 using sapdbctrl (following note 1982469).
Using latest PL191 of saphostagent.
Now, running the first command (saphostctrl without force option) starts but it was actually hanging on following:
[PID 4296] switch to user: [domain]\sybsmp
[PID 4296] Error: 5, Access is denied.[PID 4296] CreateProcessAsUser failed
[PID 4296] Updating ASE software failed. Check logfile F:\sybase\SMP\log\ASE_Suite.log for errors.
After turning off the UAC, I was able to restart the process (this time with force option), but it cancels agains on following (after 5 minutes approx):
[PID 3516] errors occured during ASE setup.
[PID 3516] LiveUpdateOption update ASE software failed
[PID 3516] *** ERROR => 'Database live update' failed: errors occured during ASE setup.
There is no more details. This is log from dev_sabdbctrl from work directory. Last entry in ASEcommon (runtime) log is that DB was shut down There is another log file - ASE_Suite.log and everything looks like finished successfully. I tried to execute syb_update_db.txt manually and it finishes successfully as well.
Checking DB it has patch level PL 02 (sql @@version), everything looks fine but I cannot be sure that it is truth.
I tried with sapdbctrl directly but it is complaining about securestore even though the entry is there and password is correct. (oh and I think force option for sapdbctrl is having typo in SAP note, somehow there appears "IDS" instead of <SAPSID>).
ERROR: Database user authentication failed: No access to SecureStore or DB_CONNECT/SYB/SADB_USER or DB_CONNECT/SYB/SADB_PASSWORD is missing in SecureStore or password is incorrect. Provide credentials for user sapsa via command input or provide access to SecureStore.
rsecssfs list (I have added SAUPDDB_USER as per note)
| DB_CONNECT/DEFAULT_DB_PASSWORD | Encrypted | 2014-10-13 10:49:52 UTC |
| DB_CONNECT/DEFAULT_DB_USER | Plaintext | 2014-10-13 10:49:50 UTC |
| DB_CONNECT/SYB/SADB_PASSWORD | Encrypted | 2014-10-13 14:17:41 UTC |
| DB_CONNECT/SYB/SADB_USER | Plaintext | 2014-10-13 14:17:34 UTC |
| DB_CONNECT/SYB/SAUPDDB_PASSWORD | Encrypted | 2014-10-13 14:09:59 UTC |
| DB_CONNECT/SYB/SAUPDDB_USER | Plaintext | 2014-10-13 14:09:51 UTC |
| DB_CONNECT/SYB/SSODB_PASSWORD | Encrypted | 2014-10-13 10:50:01 UTC |
| DB_CONNECT/SYB/SSODB_USER | Plaintext | 2014-10-13 10:49:58 UTC |
| DB_CONNECT/SYB/SYBSID_PASSWORD | Encrypted | 2014-10-13 10:50:05 UTC |
| DB_CONNECT/SYB/SYBSID_USER | Plaintext | 2014-10-13 10:50:02 UTC |
It is domain installation, central installation on 1 host.
Logs in work\SMP folder looks also fine.
Any ideas?
Thank you.
SID.log file too large
SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key
Hi All,
System copy export completed but while importing into the Target system getting below error.
Error:
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index '/BI0/F0SMD_PED1./BI0/F0SMD_PED1~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "/BI0/F0SMD_PED1~0" ON "/BI0/F0SMD_PED1" ( "KEY_0SMD_PED1P", "KEY_0SMD_PED1T", "KEY_0SMD_PED1U", "KEY_0SMD_PED11", "KEY_0SMD_PED12", "KEY_0SMD_PED13", "KEY_0SMD_PED14", "KEY_0SMD_PED15", "KEY_0SMD_PED16", "KEY_0SMD_PED17", "KEY_0SMD_PED18", "KEY_0SMD_PED19" ) with sorted_data )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '18, 160, 0, 66, 31, 67, 4, 17, 175, 3, 2, 2'
Import Monitor jobs: running 1, waiting 1, completed 42, failed 0, total 44.
Loading of 'SAPDFACT_2' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 42, failed 1, total 44.
Please advice.
Regards,
Karthik
Upgrade ASE 15.7.122 to 16 (ASEBS1600002_0-10013281)
Hello,
i am trying to upgrade my ASE installation 15.7 SP122 to version 16.0 with SAP Note 1982469 (SYB: Updating SAP ASE with saphostctrl / sapdbctrl)
Unfortunately this doesn´t work. I have sucessfully done steps 1 and 2.
In step 3 i used the command:
sapdbctrl LiveUpdate SYT -tsyb -mExecute -oTASK=UPDATE_ASE -oDROP_LOCATION="Z:\DB_Upgrade\ASE"
After a short waittime i get the following error in an outputfile called "upgrade_bs_rdbms.3496.out" in directory "C:\Program Files\SAP\hostctrl\work\SYT
===> Prepare old SAP ASE "SYT" for upgrade...
1> use master
1> sybmgmtdb..sp_sjobcontrol @name=NULL, @option="stop_js"
(return status = 0)
1> sp_configure "enable job scheduler", 0
(1 row affected)
Resulting configuration value and memory use have not changed from previous
values: new configuration value 0, previous value 0.
(return status = 0)
1> shutdown
Server SHUTDOWN by request.
ASE is terminating this process.
CT-LIBRARY error:
ct_results(): network packet layer: internal net library error: Net-Library operation terminated due to disconnect
===> Copy G:\sybase\SYT\ASE-15_0\sysam\SYT.properties to G:\sybase\SYT\ASE-16_0\sysam\SYT.properties
1 file(s) copied.
===> Upgrade SAP ASE "SYT"...
The log file for this session is 'G:\sybase\SYT\ASE-16_0\init\logs\log0910.001'.
Running task: start the SAP Server.
waiting for server 'SYT' to boot...
SERVER ERROR: Failed to boot server 'SYT'.
Task failed: start the SAP Server. Terminating configuration.
Configuration failed.
Exiting.
The log file for this session is 'G:\sybase\SYT\ASE-16_0\init\logs\log0910.001'.
Does anybody sucessfully upgraded to Version 16 and knows what kind of problem this is?
Many Thanks
Vierengel Stefan
SYBASE Upgrade from 15.7 to 16.0 Fails.
Hello Experts,
We have started a upgrade according to note 1982469.
We have used the below command
sapdbctrl LiveUpdate IDS -tsyb -mExecute -oUPDATE_FORCE=1 -oTASK=UPDATE_ASE -oDROP_LOCATION=""
Unfortunately we have come across the below error. Please help.
execution of ASE upgrade script failed. check output at "C:\Program Files\SAP\hostctrl\work\EP2"\upgrade_bs_rdbms.7196.out.
Log file : upgrade_bs_rdbms.7196.out.
init\logs\Log0531.001
G:\sybase\EP2\ASE-16_0\install\EP2.log
I see the Service SQLserver has gone down. please help how to proceed.
Thanks
Indrajith.