sir,
first I log in into system as user sidadm my case it "prdadm"
then I login into isql with sapsa user
isql -U sapsa -S PRD
password
then run backup command which I mentioned earlier.
Regards,
Sanjiv
↧
Re: sybase backup server write' call failed for device with error number 1326 (Logon failure: unknown user name or bad password)
↧
Re: sybase backup server write' call failed for device with error number 1326 (Logon failure: unknown user name or bad password)
After logon to SIDADM (PRDADM) are you able to access the share? or its asking user id and password?
BR
↧
↧
Re: sybase backup server write' call failed for device with error number 1326 (Logon failure: unknown user name or bad password)
yes I am able to access .
first time it asked for user id & password to access network shared .
I gave it & save. As mentioned before ..
next time I can access without any user id & password.
its window behavior when we connect any network shared first time its always ask for network credentials.
R
Sanjiv
↧
Re: sybase backup server write' call failed for device with error number 1326 (Logon failure: unknown user name or bad password)
Hello
It should not popup any user id & password, in that case still you are having access issue
in your network share just add the PRDADM user id with full access in the share & security level and then check the backup it should work without asking any user id and password.
BR
↧
Re: Unable to Start ASe server after upgrade to 15.7.0.130
Hi,
the log file as this entrance:
libomni1 - Component Integration Services: using 'Sybase Client-Library/15.7/P-EBF23264 SP130/X64/BUILD1570-044/OPT/Fri Jul 18 11:32:23 2014'
00:0002:00000:00001:2014/10/11 23:20:49.12 server Local cache partition number has been auto tuned to 1 for default data cache cache.
00:0002:00000:00001:2014/10/11 23:20:49.12 kernel Cannot allocate shared memory of size '425953280' bytes as this will result in exceeding 'max memory' '3072000000' bytes ('1500000' pages). ASE may retry shared memory allocation with a smaller request size.
00:0002:00000:00001:2014/10/11 23:20:49.23 server Configuration of the cache (default data cache) failed since the defined cache configuration consumes more memory than is available for buffer caches.
00:0002:00000:00001:2014/10/11 23:20:49.23 server Invalid Configuration: Unable to start Adaptive Server. The server may be started with a default configuration using the -c startserver option.
00:0002:00000:00001:2014/10/11 23:20:49.23 kernel ueshutdown: exiting
↧
↧
Re: Unable to Start ASe server after upgrade to 15.7.0.130
One level up should be a file named <servername>.cfg.
You can manually edit that file to either reduce the memory configured for data cache or (if the OS will support it) increase the "max memory" parameter to 425953280 or higher.
↧
Re: Unable to Start ASe server after upgrade to 15.7.0.130
Thanks for you assistance.
I already do that, and now i am able to start the service.
↧
Re: sybase backup server write' call failed for device with error number 1326 (Logon failure: unknown user name or bad password)
hello Sriram,
its Sybase issue.
I have login with sybsid
Go to Services.msc Select SybaseBCKServer_SID_BS
Then go to Log on Tab
Then Browse & Select sybsid User
save password & apply.
it will ask for restart services.
please stop & start service again .
then log off & login again with sybsid user
then run isql command again with network path.
this time its works..
problem is solved ...now I can take my backup into network shared location..
Thanks for your response.
Regards,
Sanjiv
SAP BASIS
↧
Re: sybase backup server write' call failed for device with error number 1326 (Logon failure: unknown user name or bad password)
Hi
Its good that you issue got resolved, Kindly close the thread
BR
↧
↧
load transaction after quiesce does not work on my Sybase ASE
Hi
How do I know that a database was in Quiesce hold gor external dump when external copy was done?
is this written in the instance log somewhere when the server is started with -q option?
Regards Tomas
↧
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.
↧
Re: load transaction after quiesce does not work on my Sybase ASE
Dear Mr Dalebjörk,
In the ASE error.log you should see some message indicating that one or several databases where set to quiesce mode when you do quiesce a database.
Also there is a built-in function is_quiesced(<dbid>) to check wheterh a database is quiesced.
When you start ASE with '-q' and you copied back the database devices files from the external dump, ASE will report for the quiesced databases that these appear to be quiesced and that it will not bring these database online automatically.
This means that if you start ASE with '-q' and the database in question is brought online automatically then it was not quiesced.
With kind regards
Tilman Model-Bosch
↧
CJS-00030 Assertion failed: Unable to set up the replication server software
Hi ,
This is sandeep. am trying to installing Replication Server on standby system.am getting following error.
SYSTEM DETAILS
sybase 15.7.0.122
replication server 15.7.0.121
suse linux 11 SP2
SWPM sp06
ERROR 2014-10-15 16:20:35.11
CJS-00030 Assertion failed: Unable to set up the replication server software. Refer to trace file sapinst_dev.log for further information.
ERROR 2014-10-15 16:20:35.361
MUT-03025 Caught ESAPinstException in module call: .
ERROR 2014-10-15 16:20:35.785
FCO-00011 The step syb_step_install_repserver_software with step key |SYB_REP_ENV|ind|ind|ind|ind|0|0|c_syb_rep_prepare|ind|ind|ind|ind|id_c_syb_rep_prepare|0|syb_step_install_repserver_software was executed with status ERROR ( Last error reported by the step: Assertion failed: Unable to set up the replication server software. Refer to trace file sapinst_dev.log for further information.).
Regards
K.sandeep
↧
↧
Sybase database : which archive log mode am I currently running?
Hi Experts,
Is there a simple way to check whenever am I running equivalent of "archive log" mode ON (trunc = false) or OFF (trunc = true)?
- via dbacockpit tcode
- and / or using an isql command ?
Many thanks, kind regards, jean
↧
Re: Sybase database : which archive log mode am I currently running?
Hi Jean.
1) DBA Cockpit: Naviagte to Space->Databases. Select a database. In the details section (tab 'Database') you will see a 'Options' group that contains 'Truncate Log in Checkpoint'.
2) With isql you can call sp_helpdb which will show you in the 'status' column if trunc log on ckpt is set. Or you access the system tables (here master..sysdatabases) directly. The information is stored in a bitmap in column status.
Regards,
Jan
↧
Re: Sybase database : which archive log mode am I currently running?
Hi Jan!
Thank you for the quick answer.
I have asked for 2 solutions... you gave me 3... you deserve the outstanding rating 
I was able to use the 2 first solutions but not the 3rd:
1) graphical view, via DBACOCKPIT : here I see "Truncate log on checkpoint = NO", which means:
- Archive log mod ON for oracle speakers
- "Full" database mode for SqlServer Speakers.
Correct ?
2.a) Via isql + sp_helpdb, I do not see "Truncate log on checkpoint" : in other words, this parameter is set to false. Correct ?
2.b) Using "master..sysdatabases", here is what I see. I do not really know how to interpret that "status" colum, probably because of the type of it ?
Feel free to add some details on 2.b) solution when you wish. Anyway I will mark your first answer as the [very] good one (I am afraid that doing it right now will close the thread).
Thanks again, kind regards, jean
↧
Re: Sybase database : which archive log mode am I currently running?
Hi Jean.
1) The meaning is more or less: All changes to the database are recorded in the log (which will fill up) and you need to take care that the log is dumped (written to a file) at regular intervals or whenever it fills up over a threshold. With the dumped log files (and a backup) you can restore the database in case of a crash. So this is the setting you want to have for any productive system (as stated in the configuration Notes e.g. 1749935). The opposite setting will automaticaly truncate the log - meaning it is lost and cannot be used for a restore.
2) Yes, sp_helpdb shows only the options that are set.
2.b) The status 8705 can be seen as binary 10001000000001 (1+512+8192). The individual bits stand for different DB options: For example the 8192 means 'allow null by default'. And 'trunc log on chkpt' is 8 which is not set in this case. Details can be found in the online documentation (SyBooks Online). Both other tools (DBA Cockpit and sp_helpdb) use the system table as the data source.
By the way: in the most recent version of the DBA Cockpit there is a new screen Configuration -> SAP Configuration Check. This will use the SAP Note mentioned above and check if the settings are matching on your system. I've attached a screenshot of a system that runs with 'trunc log on chkpt' on the SID database which will show an error.
Regards,
Jan
↧
↧
Re: Sybase database : which archive log mode am I currently running?
Great, thank you Jan. All your answers are really helpful and accurate.
Kind regards, jean
↧
Re: CJS-00030 Assertion failed: Unable to set up the replication server software
Hi,
There should be more details in the sapinst_dev.log. What is the first error message in there?
Any errors in the DR_agent log file?
Regards,
Joachim
↧
Re: Cannot connect to Sybase Server using the client
From the jTDS\README.SSL file:
At this point it should be noted that the solution has been tested against SQL
Server 2000 (SQL2K), and nothing else. Everything in this section applies to SQL
Server 2000. Having said that, the changes made to support SSL will not affect
the behavior of jTDS with other products when using plain sockets.
So SSL is not supported for SAP ASE in jTDS.
↧