When drop database fails, Please follow the below steps to drop the database.

1. Log in with a user having "sa_role".

2. Make sure the database has been marked "suspect".

The following query produces a list of all databases which are marked suspect:

1> select name from master..sysdatabases where status & 320 = 320

2> go

3. If the database is marked "suspect", go to step 4.

If it is NOT marked "suspect", Please follow the steps below :

3.1

1> use master

2> go

1> sp_configure "allow updates", 1

2> go

1> begin transaction

2> update sysdatabases set status = 320 where name = database_name

3> go

Verify that only one row was affected and then commit the transaction:

1> commit transaction

2> go

1> sp_configure "allow updates", 0

2> go

3.2.  Shut down Adaptive Server with nowait:

1> shutdown with nowait

2> go

3.3. Restart the ASE server.

4. Remove the database:

1> dbcc dbrepair(database_name,dropdb)

2> go

5. Verify that the database has been removed by executing the use database_name command.

Use of shutdown with nowait can lead to gaps in IDENTITY column values..?

can any one explain

Please refer the below steps :

1. Disk mirror duplicates the existing database device to a new location.

2. It is NOT required to initialize the new device using 'disk init' command. The mirror command will add the new device to sysdevices table.

3. After the disk mirror has been done successfully. Please unmirror the primary side of the device. This stops use of the old location and maintains exclusive use of the new location.

4. Use mode 'remove' to permanently remove the primary device.

Example:

1.  Enable Mirroring Functionality

1> use master

2> go

1> sp_configure 'disable disk mirroring', 0

2> go

Note: This static parameter is set to '1' (mirroring disabled) by default. Make sure to set it to '0' and reboot ASE.

2.  Issue the disk mirror

1> use master

2> go

1> disk mirror

2> name = "logical_device_name",

3> mirror = "physical_path_new_location.dat"

4> go

3.  After mirror completed, Please issue the unmirror to the primary side as below .

1> disk unmirror

2> name = "logical_device_name",

3> side = "primary",

4> mode = remove

5> go

80% of the attendees polled in today's webcast indicated they would likely use the workload analyzer feature released in SAP ASE 16 SP02. If you missed the live webcast today featuring Peter Dorfman detailing the new capabilities introduced with the workload analyzer, watch it now on demand: http://event.on24.com/wcc/r/1209691/B4B28AFFA8F4FE5FF8D5C347CB875693

When we migrated from Sybase client (Adaptive Server Enterprise?) 12.5 to 15.5 there were changes in the connection string format:

Under Sybase 12.5, connection strings typically looked like this:

Provider=Sybase.ASEOLEDBProvider.2;Data Source=APPLICATION;Initial Catalog=R01223;User ID=$USER;Password=$PASSWORD

The equivalent string for Sybase 15.5 looks like this:

Provider=Sybase OLEDB Provider;Data Source=application.domain.com:8000;Initial Catalog=R01223;User ID=$USER;Password=$PASSWORD

Now, in 15.7, the connection string appears to have changed again:

Provider=ASEOLDB;Data Source=application.domain.com:8000;Initial Catalog=R01223;User ID=$USER;Password=$PASSWORD

Is there a way for me to upgrade to 15.7 SP136 without having to force another connection string change?

Hi,

We are managing permissions through roles for application team members. We are encountering a permission issue post migration. We noticed that even though the roles have been granted to the logins, the user gets stuck with permission denied error.

We tried to dig deep by checking the roles and the login-role mapping in master database. The roles have all the permissions on the tables and the login is mapped to the role in sysloginroles table.

Our onshore DBA worked on this and provided the below explanation:

Whenever a role is created the role gets added in the syssrvroles table. When the role is granted permissions in a database the role gets added to the sysroles and sysusers table in the user database(Don't remember where it is added first). When migration happened, the new server has additional roles and due to the role ID mismatch the logins are getting mapped to wrong roles internally and users encounter permission denied issues.

I did understand this concept and agreed but he asked us to delete the entry for the problematic user in master database sysusers table. I did not understand this and asked him to explain further. He explained me how the permission check actually works in sybase ASE. However, I still do not seem to understand the permission checking procedure in sybase ASE.

It would be great if someone could throw some light on this issue. I would like to know the purpose of the sysroles table in master and user databases and how the permission checking happens when the permissions are granted through roles.

Please find the details below:

Pre-migration

Sybase ASE version: 12.5.4

Post migration

Sybase ASE version: 16.0

Many thanks.

--Nandy

Hi all,

I know isql has the -b parameter that suppresses table header output, but is there any way to turn it back on?  I'm running a stored procedure that outputs some data, and I'd like the headings to be in effect for that display, but to be off all the rest of the time.

Is there a SET command that can control table headers during an isql session?

Thanks and regards,

Dan

Hi All,

What exactly mean of master and query entry in interfaces file ??

Please explain.

<server_instance_name>

        master tcp ether <hostname> <port_no>

        query tcp ether <hostname><port_no>

Thanks,

Pankaj

Hi Experts,

Recently we got an error 5859,5899 with severity 16 during non business hours and the customer today in the morning addressed that he is noticing heap database errors which are specified below.

Errors from DS error log file(our end):

00:0002:00000:00002:2016/04/20 00:45:52.07 kernel  Virtual device 12 started using asynchronous (with DIRECTIO) i/o.

00:0002:00000:00002:2016/04/20 00:45:52.11 server  Error: 5859, Severity: 16, State: 1

00:0002:00000:00002:2016/04/20 00:45:52.11 server  The configuration number '652' is invalid.

00:0003:00000:00000:2016/04/20 00:45:57.60 kernel  Thread 3 (LWP 11889) of Threadpool syb_default_pool online as engine 1

00:0002:00000:00002:2016/04/20 00:45:58.00 server  Error: 5899, Severity: 16, State: 1

00:0002:00000:00002:2016/04/20 00:45:58.00 server  The value of the 'max memory' parameter (5242880) defined in the configuration file is not high enough to set the other parameter values specified in the configuration file.

Can anyone from you let me know the way to fix these errors and also is there any relation between these errors that are generated at our end with the errors that are being noticed at customer's end?

Customer noticed error details below:

Noticed there are heaps database error, insufficient privilege errors in the message log on vlhecspaci.

Apr 20 14:08:53 vlhecspaci SAPSPA_00[20461]: R47 Basis System: Deletes session T137_U20917_M0 after error Execution was canceled (Softcancel) [Warning/Session]

Apr 20 14:09:12 vlhecspaci SAPSPA_00[40938]: R47 Basis System: Deletes session T125_U20921_M0 after error Execution was canceled (Softcancel) [Warning/Session]

Apr 20 14:09:49 vlhecspaci SAPSPA_00[8112]: BY2 Database: Database error 258 at EXE

Apr 20 14:10:55 vlhecspaci SAPSPA_00[18967]: BY2 Database: Database error 258 at EXE

Apr 20 14:10:56 vlhecspaci SAPSPA_00[46425]: BY2 Database: Database error 258 at EXE

Apr 20 14:10:59 vlhecspaci SAPSPA_00[11757]: BY2 Database: Database error 258 at EXE

Apr 20 14:11:55 vlhecspaci SAPSPA_00[60609]: BY2 Database: Database error 258 at EXE

Apr 20 14:11:58 vlhecspaci SAPSPA_00[26909]: BY2 Database: Database error 258 at EXE

Apr 20 14:12:49 vlhecspaci SAPSPA_00[60609]: BY2 Database: Database error 258 at EXE

Apr 20 14:12:53 vlhecspaci SAPSPA_00[21628]: BY2 Database: Database error 258 at EXE

Apr 20 14:12:58 vlhecspaci SAPSPA_00[34944]: BY2 Database: Database error -10709 at CON

Apr 20 14:14:49 vlhecspaci SAPSPA_00[36747]: R47 Basis System: Deletes session T76_U22309_M0 after error Execution was canceled (Softcancel) [Warning/Session]

Apr 20 14:14:50 vlhecspaci SAPSPA_00[37207]: BY2 Database: Database error 258 at EXE

Apr 20 14:15:08 vlhecspaci SAPSPA_00[43014]: R47 Basis System: Deletes session T122_U22311_M0 after error Execution was canceled (Softcancel) [Warning/Session]

Apr 20 14:15:50 vlhecspaci SAPSPA_00[21661]: BY2 Database: Database error 258 at EXE

Apr 20 14:15:50 vlhecspaci SAPSPA_00[21649]: BY2 Database: Database error 258 at EXE

Apr 20 14:15:54 vlhecspaci SAPSPA_00[27710]: BY2 Database: Database error -10709 at CON

Apr 20 14:15:54 vlhecspaci SAPSPA_00[21624]: BY2 Database: Database error 258 at EXE

Apr 20 14:16:55 vlhecspaci SAPSPA_00[21637]: BY2 Database: Database error 11216 at OPC

Apr 20 14:16:55 vlhecspaci SAPSPA_00[21637]: BY0 Database: > [ASE Error SQL11216][SAP][ASE ODBC Driver][Adaptive Server

Apr 20 14:16:55 vlhecspaci SAPSPA_00[21637]: BY0 Database: > Enterprise]Internal Ct-Lib/Cs-Lib error 33816856:

Apr 20 14:16:55 vlhecspaci SAPSPA_00[21637]: BY0 Database: > 'cs_convert: cslib user api layer: common library error: The

Apr 20 14:16:55 vlhecspaci SAPSPA_00[21637]: BY0 Database: > conversion/operation was stopped due to a syntax error in th

Apr 20 14:16:57 vlhecspaci SAPSPA_00[21625]: BY2 Database: Database error 258 at EXE

Apr 20 14:17:00 vlhecspaci SAPSPA_00[21609]: BY2 Database: Database error 258 at EXE

Apr 20 14:17:51 vlhecspaci SAPSPA_00[21625]: BY2 Database: Database error 258 at EXE

Apr 20 14:17:52 vlhecspaci SAPSPA_00[55777]: BY2 Database: Database error 258 at EXE

Apr 20 14:17:52 vlhecspaci SAPSPA_00[53946]: BY2 Database: Database error 258 at EXE

Apr 20 14:17:53 vlhecspaci SAPSPA_00[26210]: BY2 Database: Database error 258 at EXE

Apr 20 14:18:50 vlhecspaci SAPSPA_00[21670]: BY2 Database: Database error 258 at EXE

Apr 20 14:19:03 vlhecspaci SAPSPA_00[27710]: BY2 Database: Database error -10709 at CON

Regards,

Dilip Voora

There is quite a lot of excitement in the air - less than a week to the grand opening of the yearly SAP conference in Las Vegas.  It is always exciting to see where SAP steers its gigantic ship - technologically speaking.  Even more - whether old good technologies like ASE are left behind or taken aboard and rehauled.  For me, in particular, 2016 event is fraught with a high load of expectations.  It is for the first time that I will be able to come literally face to face with people that drive the ship forward - both to express my collective concerns and to hear what is there stored for us in the near future.  ASE had its ups and downs.  Yet, I am still reluctant to sign it off as a technology incapable of facing the winds of change.  It's also funny that the blog post like this (Re: SAP ASE future after S/4 HANA?) infiltrate themselves into the ASE for Custom Applications arena.  Hm...

...to be continued

ATM.

Hi,

we meet a problem when trying to load a database dump.

We got error 3401 :

Error: 3401, Severity: 21, State: 1

Rec_logbounds: getnext SCAN_RID of last checkpoint failed on Rid from sysdatabases. Rid pageid = 0xb1c2a5; row num = 0x6.

This is a very big issue for us, as this concerns our production database, and we can't restore it anymore.

We use Sybase ASE 15.0, on a Linux Open Centos 7.

Thanks

TechSelect New York

Join SAP and ISUG-TECH on October 13 at the DoubleTree Metropolitan in New York City to meet the experts for a full-day of sessions focused on SAPData Management products.

We’ll provide in-depth, technical information on SAP Adaptive Server Enterprise, SAP Replication Server, and SAP IQ software, and take a deep dive into the latest product features and capabilities. What’s more, we’ll host an “Ask the Experts” panel discussion to get your questions answered by our product experts, and offer an optional track on Big Data solutions from SAP and its partners.

You will have the opportunity to:

• Get technical overviews of the latest releases and product road maps for the future
• Learn how to leverage new capabilities in SAP Adaptive Server Enterprise, SAP Replication Server, and SAP IQ
• Connect with your peers who are also using these products to discover best practices and troubleshooting tips

The registration fee (before October 13) is $149. Registration the day of the event is $299, so register online today! As an added bonus, registration includes an ISUG-TECH Gold Membership (a $299 value!)

Register now

Hi All,

One of our scheduled 'REORG DEFRAG' job is getting failed everyday with the error 12205 showed below highlighted in Red.

00:0007:00000:00099:2016/09/13 00:05:14.26 server  Beginning REORG REBUILD of index 'DBH_SNAP_INDEXES~1' on table 'DBH_SNAP_INDEXES'.

00:0006:00000:00099:2016/09/13 00:05:16.69 server  REORG REBUILD of index 'DBH_SNAP_INDEXES~1' on table 'DBH_SNAP_INDEXES' completed.

00:0006:00000:00099:2016/09/13 00:05:16.70 server  Beginning REORG DEFRAG of 'DBH_SNAP_INDEXES' partition 'DBH_SNAP_INDEXES_60524218'.

00:0007:00000:00099:2016/09/13 00:38:48.63 server  Error: 12205, Severity: 17, State: 2

00:0007:00000:00099:2016/09/13 00:38:48.63 server  Could not acquire a lock within the specified wait period. SERVER level wait period=2000 seconds, spid=99, lock type=shared table, dbid=5, objid=60524218, pageno=0, rowno=0. Aborting the transaction.

We have checked the lock wait period at server level ( using sp_configure) as well as session level(from dbacockpit-databasename-Diagnostics) and found the period is of 2000 mS and now to fix this in response to the Sybase documentation we want to increase the value of the parameter 'lock wait period' at session level(using set lock wait <time in mS(say 5000)>. At this situation few questions are running in my mind and are specified below.

1.Can we inquire the configured value of lock wait period of a session level from isql before using  - set lock wait 5000 ?

2.As the error the clearly telling the 'SERVER level wait period' should we touch the same by increasing it to 5000 from 2000 using - sp_configure by leaving away the session level (as it will be lesser than the new value at server level and the server level will take the precedence) ?

3.Is there any relation between this error 12205 and the subsequent Signal 11 errors occurred after this job failure?

Attached the error log details for your reference. Please help me with a solution to fix this at the earliest.

System Details:

Adaptive Server Enterprise/16.0 SP02 PL01/EBF 25184 SMP/P/x86_64/Enterprise Linux/ase160sp02pl00/2424/64-bit/FBO/Thu Sep 17 22:46:42 2015

Regards,

Dilip Voora

Hello,

there was an outage of the server just in the middle of an load database process.

The machine had to be restarted, so the load database was interrupted.

Actually the database is offline

Now i try to repeat <load database> but it throws the following error:

>load database mydb  from "compress::6::/backup/mydb.dmp"

>go

Msg 3142, Level 16, State 1:

Server 'XXXX', Line 3:

Cannot load database 'ACNETDB' because it is failed over.

The status in sysdatabases table is -> 44

Can you please sugest how to recover the database?

Thank you

Hi,

I'm currently trying to setup a puppet config to automate SAP ASE deployments.

https://github.com/t1m0/sap_ase_puppet

However my installation is not working on my current image, so I don't even get to the point where I could automate it.

Searching the log files for Exceptions I can only see the below error in 'opt/sybase/log/ase.log'.

RepositoryManager: Trying fallback repository location...

Execute Custom Code:

    com.sybase.ia.common.WindowsEnvironmentVariableAction was unable to be loaded: java.lang.ClassNotFoundException: com.sybase.ia.common.WindowsEnvironmentVariableAction

Below the full log of the installation.

vagrant@localhost ~]$ sudo su - sybase  -c "/opt/sybase/install/ASE_Suite/setup.bin -i silent -f /vagrant/sample_response.txt -DAGREE_TO_SAP_LICENSE=true"

Warning: You have selected '8k' as the logical page size for the SAP Adaptive

Server Enterprise. If you plan to load dump from another database, make sure

this logical page size matches the size of the source database. The default

logical page size in previous SAP Adaptive Server Enterprise versions was 2KB.

Building SAP Adaptive Server Enterprise 'SYBASE':

Writing entry into directory services...

Directory services entry complete.

Building master device...

Master device complete.

Writing RUN_SYBASE file...

RUN_SYBASE file complete.

Starting server...

Server started.

Set SA password...

SA password is set.

Building sysprocs device and sybsystemprocs database...

sysprocs device and sybsystemprocs database created.

Running installmaster script to install system stored procedures...

installmaster: 10% complete.

installmaster: 20% complete.

installmaster: 30% complete.

installmaster: 40% complete.

installmaster: 50% complete.

installmaster: 60% complete.

installmaster: 70% complete.

installmaster: 80% complete.

installmaster: 90% complete.

installmaster: 100% complete.

installmaster script complete.

Creating two-phase commit database...

Two phase commit database complete.

Extending tempdb database ...

Extending tempdb database complete.

Installing common character sets (Code Page 437, Code Page 850, ISO Latin-1,

Macintosh and HP Roman-8)...

Character sets installed.

Setting server name in SAP Adaptive Server Enterprise...

Server name added.

Enable SAP ASE for ASE Cockpit monitoring...

Task failed

Server 'SYBASE' was not created.

Building Backup Server 'SYBASE_BS':

Writing entry into directory services...

Directory services entry complete.

Writing RUN_SYBASE_BS file...

RUN_SYBASE_BS file complete.

Starting server...

Server started.

Server 'SYBASE_BS' was successfully created.

Building XP Server 'SYBASE_XP':

Writing entry into directory services...

Directory services entry complete.

Server 'SYBASE_XP' was successfully created.

'SYBASE_XP' will be started when needed by the SAP Adaptive Server Enterprise.

Building Job Scheduler 'SYBASE_JS':

Writing entry into directory services...

Directory services entry complete.

Unable to log in to SAP Adaptive Server Enterprise 'SYBASE'.

Can't install Job Scheduler stored procedures and templates.

Server 'SYBASE_JS' was not created.

Hello,

I'm wondering if this is a known issue. We are seeing the "UNMOUNT DATABASE" command hang sometimes.

The way I've been able to reproduce the issue is by filling up the disk space prior to issuing a "MOUNT DATABASE" command to force that command to fail. Then I try to issue the "UNMOUNT" command to recover from it (to rollback to a good state).

ASE Version:

Adaptive Server Enterprise/15.7/EBF 22235 SMP SP121 /P/Solaris AMD64/OS 5.10/ase157sp12x/3660/64-bit/FBO/Thu Mar 20 06:07:20 2014

Reproduction:

1. Unmount a database to create a manifest file:

UNMOUNT DATABASE [dxs5r7xPNcv733OTr3_marke] to '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-73/datafile/manifest' WITH OVERRIDE

2. Fill the disk space where the manifest file and devices reside.

3. Attempt to mount the database. This should fail due to the full disk similarly to:

1> MOUNT DATABASE [dxs5r7xPNcv733OTr3_marke] AS [dxs5r7xPNcv733OTr3_marke] FROM '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-73/datafile/manifest' USING

2>  '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-73/datafile/dxvfr723W37I7s0Vrzewc2_7.dat' = 'dxvfr723W37I7s0Vrzewc2_7_dat',

3>  '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-73/datafile/dxnF6dfL3fLo0zr3nbn4gv_2.dat' = 'dxnF6dfL3fLo0zr3nbn4gv_2_dat',

4>  '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-73/datafile/dxtyv8fZ914w4uyw9eP80t_5.dat' = 'dxtyv8fZ914w4uyw9eP80t_5_dat',

5>  '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-73/datafile/dxvelXNt54UW9xedxZa8uT_1.dat' = 'dxvelXNt54UW9xedxZa8uT_1_dat',

6>  '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-73/datafile/dx6S8O9r7Qkt7pe5749db7_0.dat' = 'dx6S8O9r7Qkt7pe5749db7_0_dat',

7>  '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-73/datafile/dxu09nflgYuv91eO1vXso7_4.dat' = 'dxu09nflgYuv91eO1vXso7_4_dat',

8>  '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-73/datafile/dxuuNmX99b0Ip7fr9O9a4q_3.dat' = 'dxuuNmX99b0Ip7fr9O9a4q_3_dat',

9>  '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-73/datafile/dxr998wB92dYpu95Vv1ked_6.dat' = 'dxr998wB92dYpu95Vv1ked_6_dat'

10> go

Msg 823, Level 24, State 2:

Server 'SRC_157_4K', Line 1:

I/O error detected during wait for BUF=0xfffffd7ffb9e8f10, MASS=0xfffffd7ffb9e8f10, Buf#=0, page=0xfffffd7ffb942000, dbid=10, Mass vdevno=25, vpage=48, Buf lpage=24, Mass stat=0x4091108, Buf stat=0x1, size=4096, cid=0

('default data cache'), Pinned xdes=0x0000000000000000, spid=0.

Msg 834, Level 20, State 4:

Server 'SRC_157_4K', Line 1:

Illegal attempt to clean buffer: BUF=0xfffffd7ffb9e8f10, MASS=0xfffffd7ffb9e8f10, Buf#=0, page=0xfffffd7ffb942000, dbid=10, Mass vdevno=25, vpage=48, Buf lpage=24, Mass stat=0x4091108, Buf stat=0x1, size=4096, cid=0

('default data cache'), Pinned xdes=0x0000000000000000, spid=0.

Msg 145, Level 14, State 10:

Server 'SRC_157_4K', Line 1:

A subquery with no aggregate functions may only contain expressions in its GROUP BY clause that are in the select-list.

4. Try to recover from the failure by unmounting the database:

1> UNMOUNT DATABASE [dxs5r7xPNcv733OTr3_marke] to '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-73/datafile/manifest'

2> go

This never returns ^^^.

NOTE: On the attempts where I was unable to reproduce the issue, the spid executing the "MOUNT DATABASE" command was terminated. I then reconnected and issued the UNMOUNT DATABASE command and it would not hang but could return an error.

Diagnostics:

1> dbcc traceon(3604)

2> go

DBCC execution completed. If DBCC printed error messages, contact a user with System Administrator (SA) role.

1> dbcc sqltext(30)

2> go

SQL Text: UNMOUNT DATABASE [dxs5r7xPNcv733OTr3_marke] to '/export/home/sybase/toolkit/564d5bfd-187c-ff17-14af-7e77caead436-staging-73/datafile/manifest'

 

 

DBCC execution completed. If DBCC printed error messages, contact a user with System Administrator (SA) role.

1> dbcc stacktrace(30)

2> go

Start dbcc stacktrace...

pc: 0x0000000001dbaef4 kpsuspend+0xa4()

pc: 0x0000000001dbdcb4 upsleepgeneric+0x2a4()

pc: 0x0000000000c15e9c dbt_get+0xf8c()

pc: 0x000000000146987f dbt_get_with_statuscheck+0xf()

pc: 0x0000000001451e16 dbcontext_change+0x36()

pc: 0x0000000001451fe2 usedb+0x42()

pc: 0x0000000001cc9b35 umt_set_dbt_unmount+0x55()

[Handler pc: 0x0000000001cc6f30 umt_handle installed by the following function:-]

pc: 0x0000000001ccc23b unmountdb+0x8b()

pc: 0x0000000000b5e008 s_execute+0x7228()

[Handler pc: 0x0000000001988460 hdl_stack installed by the following function:-]

[Handler pc: 0x000000000191e4d0 s_handle installed by the following function:-]

pc: 0x0000000000bd57ae sequencer+0x10de()

pc: 0x0000000000c72bcb tdsrecv_language+0x25b()

[Handler pc: 0x0000000001cd8020 ut_handle installed by the following function:-]

pc: 0x0000000000ba8021 conn_hdlr+0x1e81()

pc: 0x0000000001dbaff2 kpstartproc+0x32()

dbcc stacktrace finished.

DBCC execution completed. If DBCC printed error messages, contact a user with System Administrator (SA) role.

I have a customer who sometimes experiences this on AIX with ASE 15.0.3 ESD#2. Their stack trace is somewhat different. I'm not sure if this is due to version or platform differences? Or maybe it is an entirely different problem?

1> dbcc sqltext(240)

2> go

SQL Text: UNMOUNT DATABASE [dxrf0vzZdLXYz9df0f_PBMIS] to '/delphix_toolkit/toolkit/42338f9c-74c2-edac-e996-fe4127b28d4b-staging-11/datafile/manifest' WITH OVERRIDE

DBCC execution completed. If DBCC printed error messages, contact a user with System Administrator (SA) role.

1> dbcc stacktrace ( 240 )

2> go

Start dbcc stacktrace...

pc: 0x000000016b5b9b98 ()

pc: 0x0000000101c8ba68 upsleepgeneric+0x264()

pc: 0x00000001001fdadc fio__p_sema+0xe0()

pc: 0x00000001001fd430 ufopen+0x6c()

pc: 0x0000000100680d20 umtm_setup+0x1c()

pc: 0x000000010067aa98 umt_generate_manifest+0x1c()

pc: 0x000000010067ab28 umt_make_manifest+0x24()

pc: 0x000000010067b3d8 umt_create_dbmanifest+0x3c()

[Handler pc: 0x0000000100676064 umt_handle+0x0 installed by the following function:-]

pc: 0x000000010067b4a8 unmountdb+0x90()

pc: 0x000000010011f600 s_execute__fdpr_6+0xd54()

[Handler pc: 0x0000000101aa2028 hdl_stack+0x0 installed by the following function:-]

[Handler pc: 0x0000000101aab11c s_handle+0x0 installed by the following function:-]

pc: 0x0000000101cabbc8 sequencer+0x230()

pc: 0x0000000101d1f958 tdsrecv_language+0xb8()

[Handler pc: 0x0000000101aa30b0 ut_handle+0x0 installed by the following function:-]

pc: 0x0000000101ca0894 conn_hdlr__fdpr_10+0x3c()

dbcc stacktrace finished.

DBCC execution completed. If DBCC printed error messages, contact a user with System Administrator (SA) role.

 

 

1> sp_lock

2> go

The class column will display the cursor name for locks associated with a cursor for the current user and the cursor id for other users.

fid    spid   loid        locktype                     table_id    page        row    dbname          class                          context

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

      0    240         480 Ex_intent                             31           0      0 master          Non Cursor Lock

      0    240         480 Ex_intent-blk                         35           0      0 master          Non Cursor Lock

      0    240         480 Ex_table-blk                          35           0      0 master          Non Cursor Lock

      0    451         902 Sh_intent                     1020527638           0      0 master          Non Cursor Lock

 

 

(4 rows affected)

In their case it appears to hold a lock which blocks other spids:

1> sp_who

2> go

fid spid status     loginame     origname     hostname                 blk_spid dbname tempdbname cmd               block_xloid

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

   0    2 sleeping   NULL         NULL         NULL                            0 master tempdb     DEADLOCK TUNE               0

   0    3 sleeping   NULL         NULL         NULL                            0 master tempdb     ASTC HANDLER                0

   0    4 sleeping   NULL         NULL         NULL                            0 master tempdb     ASTC HANDLER                0

   0    5 sleeping   NULL         NULL         NULL                            0 master tempdb     ASTC HANDLER                0

   0    6 sleeping   NULL         NULL         NULL                            0 master tempdb     ASTC HANDLER                0

   0    7 sleeping   NULL         NULL         NULL                            0 master tempdb     CHECKPOINT SLEEP            0

   0    8 sleeping   NULL         NULL         NULL                            0 master tempdb     HK WASH                     0

   0    9 sleeping   NULL         NULL         NULL                            0 master tempdb     HK GC                       0

   0   10 sleeping   NULL         NULL         NULL                            0 master tempdb     HK CHORES                   0

   0   11 sleeping   NULL         NULL         NULL                            0 master tempdb     AUDIT PROCESS               0

   0   12 sleeping   NULL         NULL         NULL                            0 master tempdb     PORT MANAGER                0

   0   26 running    syb_sam      syb_sam      sybase_cdc1pbdbprd16vp01        0 master tempdb     INSERT                      0

   0   41 sleeping   NULL         NULL         NULL                            0 master tempdb     LICENSE HEARTBEAT           0

   0  104 sleeping   delphix_disc delphix_disc cdc1pbsybdelphixprd04           0 master tempdb     MOUNT DATABASE              0

   0  183 sleeping   NULL         NULL         NULL                            0 master tempdb     NETWORK HANDLER             0

   0  193 sleeping   delphix_disc delphix_disc cdc1pbsybdelphixprd04           0 master tempdb     MOUNT DATABASE              0

   0  233 lock sleep delphix_disc delphix_disc cdc1pbsybdelphixprd04         240 master tempdb     LOAD DATABASE               0

   0  240 sleeping   delphix_disc delphix_disc cdc1pbsybdelphixprd04           0 master tempdb     UNMOUNT DATABASE            0

The stack trace looks like it is stuck opening a file but there does not appear to be an issue with the file system:

cdc1pbdbprd8vp04:/opt/sybase/log 639>ls -la /delphix_toolkit/toolkit/42338f9c-74c2-edac-e996-fe4127b28d4b-staging-11/datafile

total 170156950

drwxr-x--x    2 sybase   sybase           12 Aug  5 20:41 .

drwxrwxr-x    5 delphix  sybase          256 Aug 11 11:32 ..

-rw-r--r--    1 sybase   sybase   33074712576 Aug 16 19:45 dx95SjqQLYUrWu0dfLfyY1_0.dat

-rw-r-----    1 sybase   sybase           24 Aug  5 18:54 dx_staging_db_name

-rw-r--r--    1 sybase   sybase   33074712576 Aug 16 19:45 dxeBL39TtegMP3mojf3Qwr_3.dat

-rw-r--r--    1 sybase   sybase   33074712576 Aug 16 19:45 dxnrv3e9333YySu335wAnH_7.dat

-rw-r--r--    1 sybase   sybase   33074712576 Aug 16 19:45 dxuvfvefXU8AvY294ts87X_1.dat

-rw-r--r--    1 sybase   sybase   33074712576 Aug 16 19:39 dxv12TXzAvf9fdvu7w6L5W_6.dat

-rw-r--r--    1 sybase   sybase   33074712576 Aug 16 19:29 dxv2l3reislx26fVAu5o39_4.dat

-rw-r--r--    1 sybase   sybase   33074712576 Aug 16 19:34 dxvbvesnQ0n7fr97wQ8jvP_5.dat

-rw-r--r--    1 sybase   sybase   33074712576 Aug 16 19:45 dxvvvv39kvUtfq1rzEx6e1_2.dat

-rw-r--r--    1 sybase   sybase         4096 Aug  9 21:35 manifest

Just curious if this is a known issue as it seems like the UNMOUNT command shouldn't hang forever. I would expect it to fail at some point.

Thanks,

Neal

Say for example if you are executing a huge sql file with each statement separated by a "go".

select 1

go

select 1

go

.......go this way up to 50000

go

select * from master..monProcessWaits

where SPID = @@spid

go

The amount of Waits for WaitEventID will be equal to the number of "go" statements in the file. We have measured the Waits and WaitTime between ASE16 and ASE157. We see the WaitTime in ASE16 is 1/3rd of what it is in ASE157.

Why is this so important?

If you are running some benchmarking tests between ASE157 and ASE16 then this becomes an important factor. It will never be like for like.

However, we think this is a good improvement in ASE16 and will help improve elapse times.