Quantcast
Channel: SCN: Message List - SAP Applications on SAP Adaptive Server Enterprise (SAP ASE)
Viewing all 3678 articles
Browse latest View live
↧

Re: How to apply transaction log backup in Sybase

February 20, 2014, 7:49 am
$
0
0

Well, your source output shows the size of  NRD as

NRD

           233472.0 MB

 

which matches the error you get when you try to load its dump into the destination

 

"Data on dump will not fit into current database. Need 233472 Mbyte database"

 

Your output on destination shows the NRD database is much smaller:

 

NRD

           161792.0 MB

 

 

So you either didn't create NRD on destination using the script generated by list_only=create_sql, or some of your devices don't have enough free space

on them to create the database as specified.  (a quirk of the CREATE and ALTER database commands is that if you ask for a certain amount of space and there is some space but not as much as you are asking for, ASE will allocate the available space but not raise an error - you have to be a little sharp-eyed to see that the size it reports back is smaller than what you actually asked for.).

 

To get the dump to load, the destination NRD will need to be enlarged to 244472 MB in size.

 

-bret

↧
Search

Re: How to apply transaction log backup in Sybase

February 20, 2014, 8:12 am
$
0
0

Typo on my last line there, that should be 233472 MB.

↧
↧

Re: How to apply transaction log backup in Sybase

February 20, 2014, 8:18 am
$
0
0

Hi Bret,

 

 

So how i can start restoration.What i have to do now?How can i make size equivalent or bigger that source one.

 

Regards

↧

Re: How to apply transaction log backup in Sybase

February 20, 2014, 10:19 am
$
0
0

In general, either use ALTER DATABASE to add more space to the database, or completely drop and rebuild it.

 

If you don't have enough room on the existing devices, you can create new devices using

DISK INIT or possibly enlarge existing devices using DISK RESIZE.

↧

Re: How to apply transaction log backup in Sybase

February 21, 2014, 2:10 am
$
0
0

Hi Adil,

 

In my opinion, this is a document which should be read by anyone who is dealing with Sybase ASE:

Getting Started with SAP Applications Using SAP Adaptive Server Enterprise

 

On this specific topic, there are few notes that will offer you basically a step-by-step guide to create a backup strategy and restoration procedure:

1585981 - SYB: Ensuring Recoverability for Sybase ASE - Please be carefull about parameters configuration, especially 'trunc log on chkpt', which I noticed is enabled in your case...

sp_ddlgen 'database', NRD command should help, but the best approach would be to use (it will offer you the dboptions, which are extremelly important):

load database NRD with listonly = 'CREATE_SQL'

go

, as stated by Mark and confirmed by Bret , according to:

1611715 - SYB: How to restore a Sybase ASE database server
(Windows)

1618817 - SYB: How to restore a Sybase ASE database server
(UNIX)

 

Based on the given information, you should now be able to solve your issue.

 

Kind Regards,

Ionut

↧
↧

Re: How to apply transaction log backup in Sybase

February 21, 2014, 11:30 pm
$
0
0

Hi Bret,

 

I follow these step:-

1.delete datafiles from /sybase/NRD/sapdata1/NRD_data_001.dat

repeat same for all four datafile.

isql -Usapsa  -SNRD

use master

go

2.drop database NRD

3.execute this command:-

 

disk init name='NRD_data_001', physname='/sybase/NRD/sapdata1/NRD_data_001', size ='90000M', directio='true'

disk init name='NRD_data_002', physname='/sybase/NRD/sapdata2/NRD_data_002', size ='80000M', directio='true'

disk init name='NRD_data_008', physname='/sybase/NRD/sapdata3/NRD_data_008', size ='90000M', directio='true'

disk init name='NRD_data_009', physname='/sybase/NRD/sapdata4/NRD_data_009', size ='90000M',

 

error giving:- NRD_data_001 already exsist.But i have already deleted it.

 

pls suggest

 

Regards

Adil

↧

Re: How to apply transaction log backup in Sybase

February 22, 2014, 4:47 am
$
0
0

To drop a device you want to:

 

- remove all databases from device

- drop the device from the dataserver (via sp_dropdevice)

- if the device is a file out in the OS then remove said file

 

If your disk init is failing with a message about a device already existing then it's usually a) the device already exists (sp_helpdevice NRD_DATA_001) and you need to first sp_dropdevice NRD_DATA_001 or b) the OS file exists and you need to rm it.  At this point it's hard to tell which is the case because we haven't been given the actual error message.

 

For future reference, please post the entire output/error message as there are usually some key details in said message.

↧

Re: How to apply transaction log backup in Sybase

February 22, 2014, 8:25 am
$
0
0

Hi Mark,

 

Thanks for ur support . As i was getting error while creating NRD_DATA_001 so i created NRD_DATA_005 like /sybase/SID/sapdata1/NRD_data_005 .. and i did same with all  device and i start restoration again .

It completed successfully But now i am getting error while starting sap instance

Below is error detail.

 

[ASE Error SQL4002]Login failed.

[dbsh         1249]

B  ***LOG BY2=> sql error 4002   performing CON [dblink       550]

B  ***LOG BY0=> [ASE Error SQL1640]Adaptive Server requires encryption of the lo

gin password on the network.

[ASE Error SQL4002]Login failed.

[dblink       550]

M  ***LOG R19=> ThDbConnect, db_connect ( DB-Connect 000256) [thDatabase.c 70]

M  in_ThErrHandle: 1

M  *** ERROR => ThInit: db_connect (step TH_INIT, thRc ERROR-DB-CONNECT_ERROR, a

ction STOP_WP, level 1) [thxxhead.c   2147]

 

Regards

↧
Search

Re: How to apply transaction log backup in Sybase

February 22, 2014, 9:20 am
$
0
0

This same issue came up in another discussion in this forum: http://scn.sap.com/thread/3461308

 

The gist of the solution is that you need to log into the dataserver and issue:

 

sp_configure 'net password encryption reqd', 2

↧
↧

Re: How to apply transaction log backup in Sybase

February 22, 2014, 9:30 am
$
0
0

Hi Mark,

 

I done same but still error while connecting SAP.

 

% isql -Usa -SNRD -X

Password:

1> sp_configure 'net password encryption reqd',1

2> go

Parameter Name                 Default     Memory Used Config Value

         Run Value    Unit                 Type

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

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

net password encryption reqd             0           0            1

                    1 switch               dynamic

 

 

(1 row affected)

Configuration option changed. ASE need not be rebooted since the option is

dynamic.

Changing the value of 'net password encryption reqd' does not increase the

amount of memory Adaptive Server uses.

(return status = 0)

 

But still facing same error....I restarted server but still coming!!!!

↧

SYBASE unable to Create a dump configuration

February 23, 2014, 4:18 am
$
0
0

Hi All,

 

We  have installed a new crm 7.0 ehp3 with Sybase database on 2008 r2

Now we trying to setup the database backup and trans log backup

 

I followed the note 1588386  when we try connect to db

it gives the error we also tried unlocking the sa account.

 

below Is the error we are facing

↧

Re: SYBASE unable to Create a dump configuration

February 23, 2014, 5:12 am
↧

DBA planning calendar

February 24, 2014, 3:32 am
$
0
0

Hello,

 

I'm getting several errors with scheduled jobs. But It's so rare, sometimesit works, sometimesnot.

 

I've scheduled the backup of transaction log, DB, and master.

 

--SAP DBA Planning Calendar: SQL Script

print( SELECT "starting job execution at " || str_replace(convert(VARCHAR(20),getdate(),23),"T","") )

dump transaction PRD using config = 'PRDLOG'

go

print( SELECT "job execution finished at " || str_replace(convert(VARCHAR(20),getdate(),23),"T","") )

 

I've defined a store procedure for backup.

 

The job for master backup, It always fails.

 

--SAP DBA Planning Calendar: SQL Script

print( SELECT "starting job execution at " || str_replace(convert(VARCHAR(20),getdate(),23),"T","") )

--SAP DBA Planning Calendar: SQL Script

print( SELECT "starting job execution at " || str_replace(convert(VARCHAR(20),getdate(),23),"T","") )

dump database master using config = 'master'

go

print( SELECT "job execution finished at " || str_replace(convert(VARCHAR(20),getdate(),23),"T","") )

print( SELECT "job execution finished at " || str_replace(convert(VARCHAR(20),getdate(),23),"T","") )

 

 

I´ve checked partition space but this isn't the reason.

↧
↧

Re: DBA planning calendar

February 24, 2014, 3:47 am
$
0
0

Hi Rubben,

 

Is DBA Cockpit Correction Collection at latest version?

I allways run the dump database command in Planning Calendar like this:

use master

go

dump database master using config = 'master'

go

 

in order to avoid any issues. Please let me know if it helps.

 

Regards,

Ionut

↧

Re: DBA planning calendar

February 24, 2014, 5:14 am
$
0
0

You may want to consider posting the complete error message(s) you're receiving.

 

In the case of backup failures you may also want to check the dataserver and backupserver errorlogs for any additional details that may be of assistance in addressing the problem. (Posting said errorlog details to this discussion would also be recommended.)

↧
Search

Re: DBA planning calendar

February 24, 2014, 7:22 am
$
0
0

Hi Ruben,

 

Could you also share following details

1) What is the Sybase Version

2) How many app servers does production server has

3) Have you applied all the dbacockpit related notes ?

 

Regards,

Deepak Kori

↧

ASE service Syabase SQLServer_"SID" don't start

February 24, 2014, 9:18 am
$
0
0


Hi,

 

We have shutdown the ASE Server, after that we tried to start it insuccefully. with the msg

"The Sybase SQLServer_"SID" service on "host" started and then stopeped.Somme services stop automatically are no in use by other services or programs"

 

We have checked the log SID.log, where we have see that the saptools  has defalut segment full

 

Can't allocate space for object 'DBH_MSG_LOG' in database 'saptools' 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.

 

00:0000:00000:00000:2014/02/24 13:45:50.22 kernel  SySAM: Checked out license for 8 ASE_COMPRESSION (2014.1231/permanent/1296 8FE3 0A83 A167).

00:0000:00000:00000:2014/02/24 13:45:50.22 kernel  Checked out license ASE_COMPRESSION

00:0000:00000:00000:2014/02/24 13:45:50.24 kernel  SySAM: Checked out license for 8 ASE_ASM (2014.1231/permanent/1296 8FE3 0A83 A167).

00:0000:00000:00000:2014/02/24 13:45:50.24 kernel  Checked out license ASE_ASM

00:0000:00000:00000:2014/02/24 15:04:20.87 kernel  SySAM: Using licenses from: D:\sybase\"SID"\\SYSAM-2_0\licenses\SYBASE.lic;D:\sybase\"SID"\\SYSAM-2_0\licenses\SYBASE_ASE_DE.lic

00:0000:00000:00000:2014/02/24 15:04:21.24 kernel  SySAM: Checked out license for 8 ASE_CORE (2014.1231/permanent/1296 8FE3 0A83 A167).

00:0000:00000:00000:2014/02/24 15:04:21.24 kernel  This product is licensed to: SAP, for use with SAP Business Applications.

00:0000:00000:00000:2014/02/24 15:04:21.24 kernel  Checked out license ASE_CORE

00:0000:00000:00000:2014/02/24 15:04:21.24 kernel  Adaptive Server Enterprise (Enterprise Edition)

00:0000:00000:00000:2014/02/24 15:04:21.24 kernel  Using config area from primary master device.

00:0000:00000:00000:2014/02/24 15:04:21.26 kernel  Warning: Using default file 'D:\sybase\"SID"\"SID".cfg' since a configuration file was not specified. Specify a configuration file name in the RUNSERVER file to avoid this message.

00:0000:00000:00000:2014/02/24 15:04:21.26 server  The dump history file version is missing or invalid.

00:0000:00000:00000:2014/02/24 15:04:21.26 server  Verification failed for parameter 'enable dump history'.

00:0000:00000:00000:2014/02/24 15:04:21.26 server  The dump history file version is missing or invalid.

00:0000:00000:00000:2014/02/24 15:04:21.26 server  Verification failed for parameter 'dump history filename'.

00:0000:00000:00000:2014/02/24 15:04:21.26 kernel  The value of the option 'number of engines at startup' is not set to its default. This option has no effect in threaded mode.

00:0000:00000:00000:2014/02/24 15:04:21.26 kernel  SySAM: Checked out license for 8 ASE_PARTITIONS (2014.1231/permanent/1296 8FE3 0A83 A167).

00:0000:00000:00000:2014/02/24 15:04:21.26 kernel  Checked out license ASE_PARTITIONS

00:0000:00000:00000:2014/02/24 15:04:21.28 kernel  SySAM: Checked out license for 8 ASE_COMPRESSION (2014.1231/permanent/1296 8FE3 0A83 A167).

00:0000:00000:00000:2014/02/24 15:04:21.28 kernel  Checked out license ASE_COMPRESSION

00:0000:00000:00000:2014/02/24 15:04:21.28 kernel  SySAM: Checked out license for 8 ASE_ASM (2014.1231/permanent/1296 8FE3 0A83 A167).

00:0000:00000:00000:2014/02/24 15:04:21.28 kernel  Checked out license ASE_ASM

 

At this moment we are unable to logon using isql.exe, this is normal because the ASE isn´t started.

 

Have any advice to solve this?

 

Thanks in adcance for your help.

↧
↧

Re: ASE  service Syabase SQLServer_"SID" don't start

February 24, 2014, 10:55 am
$
0
0

Hi Alcino,

 

I would not expect an "out of space" error on any database but master (and maybe sybsecurity if auditing was on) to prevent ASE from at least booting.

 

Is

00:0000:00000:00000:2014/02/24 15:04:21.28 kernel  Checked out license ASE_ASM

really the last message in the ASE log?

 

If you look back in the log to the previous time ASE succesfully booted, what was output to the log just after that entry (that is likely going to be related to whatever is causing the server not to boot now).

 

On my own PC, running a 15.7 ESD 1, without all the licenses you have, what I see is:

 

00:0000:00000:00000:2013/08/13 15:13:06.73 kernel  Using config area from primary master device.

00:0000:00000:00000:2013/08/13 15:13:06.73 kernel  Warning: Using default file 'C:\Sybase\REL157_bret_pc.cfg' since a configuration file was not specified. Specify a configuration file name in the RUNSERVER file to avoid this message.

00:0000:00000:00000:2013/08/13 15:13:06.97 kernel  Kernel memory at 0x20000000, 99518464 bytes

00:0000:00000:00000:2013/08/13 15:13:06.97 kernel  Kernel memory at 0x20000000, 1275904 bytes

00:0000:00000:00000:2013/08/13 15:13:06.97 kernel  Server part of first shared memory region at 0x20137800, 98242560 bytes.

00

 

So I suspect your ASE may be having trouble allocating shared memory for some reason.

 

But it seems strange there is no actual failure message after your ASE checked out the license.

 

-bret

↧

Re: ASE  service Syabase SQLServer_"SID" don't start

February 24, 2014, 11:38 am
$
0
0

Hello Bret,

 

Thank you for your reply.

 

Maybe you're right concerning the license issue, but i don't understand how cand this change during a shutdown!!!

 

Looking to the shared memory, as you said that can be the reason too!

 

How can i check the license, and shared memory knowing that I 'm not able to  connect to the ASE server?

 

Thank you,

Alcino

↧

Re: ASE  service Syabase SQLServer_"SID" don't start

February 24, 2014, 12:29 pm
$
0
0

Hi Alcino,

 

Does your older boot sequence in the log show some other license normally getting checked out as the next thing after checking out ASE_ASM?  Or does it proceed to show a "kernel memory" allocation next?

 

If it looks like a license might be next, there might be some error in the SYSAM log

in $SYBASE\SYSAM-2_0\log

 

I'm not greatly knowledgable on Windows.  For memory issues on a UNIX platform I'd start by looking at "ipcs -m" to see what was already out there for allocated shared memory.  On Windows, I think you can monitor memory by starting up the Task Manager, under the Permformance tab is a "resource monitor" button which takes you to a screen with a memory tab.  That might show if there is something out there hogging memory.

 

You could also try modifying the configuration file (perhaps just copying in an older version) just to see if the server would boot if it had much lower memory requirements.  (that isn't meant as a solution, just a diagnostic step.  You presumably don't want to go into production with the configurations set to a minimal state).

 

And you might look at the recent configuration files to see if there were any major changes since the last time ASE booted.

 

-bret

↧
Viewing all 3678 articles
Browse latest View live
Search