I have a backup of a database and restore it on another testing server. All data caches is empty. so I want to load data in to cache for testing. basically I need to choose tables and indexes to loaded manually with query. But if I want to fill up all caches, if dbcc checkdb will do this for me?

I have installed Sybase ASE 15.7 on CentOS 6.3 with command line with terminal. Where to find out sybase central? Need to install it separately?

Have checked folder, there is no folder like $Sybase/Shared/Sybase Central 6.0.0/...

If need to install separately, where to download the package?

I am running a SAP Solution Manager 7.1 on Sybase ASE 15.7.0.110. The InfoCube table /BI0/F0SMD_PE2H keeps on growing quickly. This wasn't the case on other RDBMS. The ATM job doesn't help. Also running the ATM job manually doesn't change the table size:

reorg compact [SMP.SAPSR3./BI0/F0SMD_PE2H]

Only if I use the rebuild option, the table size shrinks:

reorg rebuild [SMP.SAPSR3./BI0/F0SMD_PE2H]

This causes the InfoCube with 1 million rows to shrink from 8 GB to 400 MB. That was an awful lot of wasted space.

Is it possible to avoid this excessive growth? Looks like the daily data load is causing the table to grow quickly again.

Or should I try to perform this "reorg rebuild" via the weekly ATM job?

Regards,

Mark

Good afternoon, I'm trying to export a report to Excel, the report has headers, but when I generate in excel do not appear any header, I want one I collaborate telling me as I do to display my headers in the exported document in Excel? . thanks

Some migrations are easy and pain free and almost an after thought.  But eventually, we all get to the fun ones - the mission critical ERP implementation that is the life-blood of the business.  You know the one - the one if it even has a minor hiccup, the CEO will be livid because your customers are severely inconvenienced.  I have seen a lot of these projects succeed…..and I have watched others struggle mightily.  From it all, I have learned that there 5 key
critical success factors to successful migrations of business critical ERP systems to ASE.

1. Use the Best Practices for Migration and supplement with an OS DB migration expert and expert DBA resources.
2. Have a performance & capacity team of DBAs, ABAP and OS admins that are aligned and committed to the success of the project.
3. Make sure you set up and use a current version of DBA Cockpit
4. Tune and monitor the statement cache
5. Attack the top n problem queries in iterations

I have found that if you follow these guidelines, most of what is left is fine tuning and if any problems arise, they can be quickly resolved.

1 - Best Practices for Migration

Okay, this is not a shameless plug….it is more of a mea culpa.  It has been a while since this has been updated.  Sorry.   The first iteration of the SAP on ASE Best Practices was actually split into two - one for migration (SAP Note 1680803) and one for runtime (SAP Note 1722359).  At the time, it was felt due to all of the runtime tuning optimizations that to have it all in a single document was a bit much.  In these days of twitter, apparently anything long than 140 characters or 3 pages is considered too difficult to expect people to read.   Hmmmmmm.....back in my day, we had books.   We actually read them.

However, subsequently, a lot of the runtime recommendations have been moved to their own SAP Notes - which should be considered by any customer.  As we have started updating the last version for the newer ASE releases and incorporating the lessons we have learned and the features added to support SAP, we are probably going to pull it back into one document - but still with the links to some of the optional optimizations, etc.  Hopefully,we should have out in a few more weeks (it is in review).

However, the version that is there does contain a lot of useful information.  Some of it may be dated and there may be faster/better ways to accomplish step whatever using new feature X in ASE service pack Y - but that is why you need an expert DBA resource (or more) that can review it.  Now, by expert DBA resource, I am not talking someone that can merely spell ASE or has worked on it some - I am talking someone who will likely be a key part of the performance and capacity team (next topic) and thoroughly understands ASE performance with respect to memory/caches, query performance and parallel processing.  Their key role here is to look at which features will ease your migration effort and downtime and facilitate the initial performance analysis in stabilizing the system.  If you do not have such a person within your company, you may wish to hire someone or contract for a decent period of time.  Yeah, both these options are likely expensive as really good DBA’s don’t come cheap….but….think about it.  If the system you are migrating controls the life of your company and is responsible for 100’s of millions or billions of dollars in revenue…..outsourcing to a cheap resource just to reduce the cost of the migration is likely going to result in high risks.  Outsourcing for supplemental operational experience (performing backups, monitoring error logs, etc.) is a workable solution to providing short term or long term supplemental staffing - however, you should make sure they are using DBA Cockpit.

The second resource that is invaluable is an OS/DB migration expert.  I am not talking about merely certified - I am referring to someone who has done this multiple times.  I mention this from an experience I had with working with someone from whom I learned a ton of invaluable information about migrations - e.g. leveraging DISTMON and other aspects that could dramatically reduce the time and ease the complexity.  Again, much like the expert DBA resource, an OS/DB migration expert is likely not cheap - but the good news is that unless you have a plethora of landscapes, this is a more temporary staffing requirement.

2 - Performance & Capacity Team

I mention this based on my experiences.  One of my first experiences with this was that it was obvious that while the executives were committed to the migration for the cost savings, the company’s core ABAP developers were adamantly opposed to a migration.  While the migration happened - getting resolution to problems was an absolute nightmare.  In addition, SAP ERP systems can often be best debugged when the team works together - in this case, there was none of that.  It was almost a constant badgering of “well on platform X, we never had to do that”.  First, like many folks, they missed the fact in the big picture that the migration to ASE almost always requires an upgrade to the SAP BASIS and kernel layers as well as a DBMS migration - and any changes to the application layer are much more intrusive.  Second problem was they had outsourced the hardware and OS implementation to a group who sort of did a fire-and-forget implementation without any consultation with the DBA staff or even ABAP team.  As a result, the customer struggled with environment issues for months.  Unfortunately, the later experience has been repeated all too often when OS admins simply install the system and strongly resist any OS tuning recommendations from either the ABAP or DBA staff and tend to argue the merits of their implementation based on a generic “best practices” vs. understanding the SAP NetWeaver or ASE can benefit from specific OS tuning.

By contrast, I worked on a project where the OS vendor was committed and provided onsite support and did a ton of knowledge transfer and tools skills to the project staff.  They weren't there every day - but they were there periodically and on the actual migration date.  It made a real impression and changed my opinion of that company.  They made sure that the tools and graphs were not hidden deep in the bowels of the sysadmin lair where they never see the light of day - but rather they were used.  I remember walking into a meeting by the project manager where he pulled up the OS tools and showed the HW utilization graph by component (CPU, network, disk) during one of the migration test runs and challenged us with what we could do to utilize the HW more effectively to reduce the migration.  Not only was it extremely useful as we noted a common HW configuration issue (10GbE running at 1GbE) but it help us to see the need to have a separate migration configuration of more cores/memory vs. a runtime configuration and we worked together on how to best do this to minimize downtime and effort.

This extends beyond the migration and long into production monitoring and capacity.  As workload increases, all need to be aware of the trends of HW utilization by the various components and how that utilization has changed over time.  One of the worst things I have seen is that often after the system is in production, no one seems to be able to come up with even the simplest of graphs/charts highlighting performance trends - whether HW utilization, key transaction times, or DB key performance indicators and trends.

3 - Use DBA Cockpit

This is puzzling to me.  SAP has spent a lot of time obfuscating the DBMS complexities and command differences behind a single GUI that focuses on SAP application requirements….and people don’t even try it…and often don’t even set it up.  Now, I have to admit to be an old, grey-haired geezer that things the ultimate editor is ‘vi’ - but I, myself, am impressed with DBA Cockpit - especially as two of the most critical and common performance issues (statement cache and query tuning) is simplified and easy to get to.  My first real experience with DBA Cockpit was helping out during an internal SAP IT migration of one of SAP’s internal systems…..people who know me know all too well my preference and heavy use of command line tools and scripts…and to say I was sold on DBA Cockpit would likely stun them with disbelief.  There are still some aspects (such as deep query diagnostics) that I like to do manually - but from a performance monitoring/problem query isolation perspective - DBA Cockpit to me is a no brainer.

The other reason this is puzzling to me is that a lot of the drudgery DBA tasks such as update stats, reorg, etc. are automated in DBA Cockpit via the ATM jobs.  Even if you find the ATM implementation insufficient for your largest tables (as one customer complained), having it manage 59990 of the tables in the schema while you develop a more focused solution for the top 10 largest tables reduces the amount of effort needed to develop the custom solution.

Also, make sure you are using a current version.  A recent customer decided in their migration to simply upgrade their SAP layer to just the minimums needed to support ASE as this represented the closest release to their current version.  The result was they got DBA Cockpit v1.0.  While it had a lot of the functionality they were after, the current release at the time was something like v23.  It had a LOT more functionality, fixes, and improvements and was a lot more easy to use.  Now, one of the things I often suggest in a large mission critical system is that there is a DBA host from where DBA monitoring and custom DBA scripts reside - a separate system from the DBMS host.  It should be a simple task to implement a more current version of the SAP NetWeaver kernel on that host so that a more current release of DBA Cockpit can be used.  Lacking such a DBA host and assuming that all DBA work will be done on the DBMS host is clearly a recipe for catastrophic failure….one oooopps at the filesystem and something reeeallllly bad happens next.  Isolation is the key to stability.

4 - Tune and Monitor Statement Cache

My first exposure to this problem was at a customer that was having debilitating CPU spikes.  We spent hours looking for the usual culprits - bad queries, application loops, etc.  And then the person with the least experience with ASE in the room points out the statement cache….ughhhh.  In a matter of minutes and several iterations of increasing it - problem solved.

The statement cache is ASE is probably one of the most critical areas of ASE from a performance perspective for SAP applications.  Not only is sizing it correctly a key factor - but also it is the entry point for all of the query tuning diagnosis.   Unfortunately, the default is 100MB.  For most mission critical systems, this is about 10% of the real requirement of ~1GB.  Some sites may need 2GB.  Keeping in mind that the correct size will depend on a lot of factors such as the breadth of different queries as well as the transaction rate, I might start with 250MB as a minimum for most small system installs and 1GB for larger systems and 2GB for VLDB.  Then monitor and increase the size when you see considerable turnover occurring.  By considerable, I mean any consistent turnover of 10% of the statements in cache.

This is where DBA Cockpit excels.  If you simply look at the statement cache, the first chart you will see is something like the following:

It shows us that there are about 14,500 statements in cache with a single cache hit ratio drop to ~80%.  Now, those that know me also know how much I hate cache hit ratio metrics.  It may have been a really good metric several decades ago when memory was expensive and we didn’t have much of it.  But in today’s large memory systems, it is almost useless.  An in-memory table scan is an incredible waste of both CPU and memory - but yet will drive cache hit ratio to 100%.  Consequently, I like to focus on cache volatility and try to find out what is causing cache fluctuations.  To do this, I prefer to see how many statements were removed and inserted - more a graph similar to:

This of course points out one of the other neat features of DBA Cockpit - the ability to create and save custom user-defined graphics.  Now, with 14,500 statements a sudden turnover of 2000 of them could be a concern if it continues.  It could be due to someone running sp_recompile on a lot of tables, so a single spike such as the above is not a source for immediate concern - however, it is a bell ringer to start paying close attention

5 - Top N Problem Queries

During the initial migration testing, someone should have identified key business transactions and compared the pre-migration to post-migration execution times and resolved any of those problems prior to migration.  However, once the migration is complete and the system is in production, you need to focus on the rest of the system and how it is impacted by the migration.  Reviewing every query in every module simply isn’t possible.  The best approach I have found is to simply start tackling the top 5 or so bad queries - resolve them - and then repeat.  After about 3-4 iterations, suddenly the system performance is so stable/predictable that it becomes almost boring - but still a good practice aspect for up and coming members of the performance and capacity team.

Again, this is where DBA Cockpit shines - one of the (in my mind) key displays it has is the top N bad queries.  Now, I like to customize this by adding in columns such as SSQLID, Hashkey, TotalLIO, TotalCPUTime, and TotalElapsedTime and then saving that as the new default for the display.   Once you have identified the top 5 queries, you may need to consider one of several actions:

• Add a better index.  The fact that a query uses an index is not good enough - it should use an effective index and the more often the query is executed the more closely there should be an index that matches the predicates.  It is fine for a query executed once a day to use partial index techniques…..a query that is executed millions of times a day needs an index to support it.
• Add histograms steps.  It is a bit much to go into here, but the default histogram steps of 20 is too low for SAP - 50 is better - and for tables with large IN() or UNION clauses, 100 might be needed.
• Better histogram cell or density stats than the default options collect.
• Slight query modifications (to aid in costing or execution speed)
• Altering the query to add a hint via a PLAN clause

The last one is a last resort solution - although it may be a temporary solution implemented quickly to work-around the problem and restore business execution while diagnosing the real issue.  However, these query optimization techniques are likely best left as a topic for another day.

Hi Experts,

We need to take a backup of SAP ECC system installed on Sybase ASE 15.7 and I could find the below SAP notes :

• 1585981   SYB: Ensuring Recoverability for Sybase ASE
• 1588316   SYB: Configure automatic database and log backups
• 1618817   SYB: How to restore a Sybase ASE database server (UNIX)

As per the note 1588316 could understand that by DUMP DATABASE and DUMP TRANSACTION we can take the backup and I assume it is online backup.

So I would like to understand

• How to take an offline backup? I believe this is more reliable as we are patching our DEV system and need a backup. Please advice
• Using the backup taken with the above method can we restore the backup on a different machine ?
• How would the procedure differ from restoring on same server to different server
• What would be the compression % ff I had to backup the data to a local file system how much space I would need ?

Thanks !!

Regards,

Srikanth

hello!

Help mesolve the problem.

I have erp6ehp6 - Sybase ASE 15.7 - Windows server 2008

I want to configure DBA Cockpit

But it tr.DBACOCKPIT I get themessage:

Maintenance is not allowed for local connect user SAPSR3

But in tr. DBCO I see:

DB Connection:  +++SYBADM
DBMS: SYB
User Name: sapsa
DB password:
Conn. info: SYBASE_DBNAME=SNB SYBASE_DBOWNER=SAPSR3 SYBASE_SERVER=sandbox

Connection Limit   0
Optimum Conns      0

What am Idoing wrong?

HI Friends,

I am new to ASE.. have mostly worked on Oracle.

I have installed a sap system on Sybase. I need to know how can i enable Automatic DB Expansion feature which i think i didnt selected during installation.

I dont want to do this from DBACOCKPIT as this is not working properly and I need to run SGEN.

please help.

Hi Experts,

We are currently performing a stack upgrade on SAP ECC 6.0 EHP6 to SP11 and got struck in pre-processing phase because DB is not available :

When checked understood from trans.log that log segment is full:

***LOG BY0=>[ASE Error SQL1105]Can't allocate space for object 'syslogs' in database 'ECD' because 'logsegment' 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.

So tried dumping the transaction log and increasing the log file by 8MB and restarted but same error ::

isql -Usa Password:<SA_PASSWORD> 1> use master 2> go 1> dump transaction master with no_log 2> go

1> alter database master 2> log on master = 8 3> with override 4> go

Then we tried increasing the size of the segment'logsegment' as mentioned in the errorlog with :

1> sp_extendsegment logsegment, master, master

2> go

But it returned:

Msg 17793, Level 16, State 1:

Server 'ECD', Procedure 'sp_extendsegment', Line 349:

System Administrator (SA) must set database 'master' to single-user mode with

sp_dboption before using 'sp_extendsegment'.

(return status = 1)

Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRAN is

missing. Previous count = 0, Current count = 1.

I tried logging in with sa user and put master to single user mode it returned as below :

1> use master

2> go

1> EXEC sp_dboption master, 'Single User', True

2> go

Msg 17422, Level 16, State 1:

Server 'ECD', Procedure 'sp_dboption', Line 387:

The 'master' database's options cannot be changed.

(return status = 1)

Iam clueless now. could you please advice ?

Regards,

Srikanth

Hi

My production system is on SAP ECC 6.0 on Sybase DB and HP Unix 11. The
customer want to create a DR system on Linux with same database
version.

Pl suggest and clarify

1. Is it possible ?
2. which tools to be used ?
3. DR is on different location using WAN

Regards

Vimal

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 All ,

i install the ECC IDES 6.0 EHP6 sybase Adaptive Server Enterprise 15.7 on win  2008 X64 .

using install master.  at the last  check ddic password step.message error.  

"Test logon to SAP System IDS failed.   SOLUTION: Make sure that the system is started, that the user DDIC exists and that the password of user DDIC is correct."

Kindly look into the following dev_w0.log

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

trc file: "dev_w0", trc level: 1, release: "720"

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

*

*  ACTIVE TRACE LEVEL           1

*  ACTIVE TRACE COMPONENTS      all, MJ

*

M sysno      00

M sid        IDS

M systemid   562 (PC with Windows NT)

M relno      7200

M patchlevel 0

M patchno    210

M intno      20020600

M make       multithreaded, Unicode, 64 bit, optimized

M profile    \\EGSPL-IDS\sapmnt\IDS\SYS\profile\IDS_DVEBMGS00_EGSPL-IDS

M pid        3820

M

M  kernel runs with dp version 133000(ext=118000) (@(#) DPLIB-INT-VERSION-133000-UC)

M  length of sys_adm_ext is 588 bytes

M  ***LOG Q0Q=> tskh_init, WPStart (Workp. 0 3820) [dpxxdisp.c   1377]

I  MtxInit: 30000 0 0

M  DpSysAdmExtCreate: ABAP is active

M  DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active

M  DpIPCInit2: read dp-profile-values from sys_adm_ext

M  DpShMCreate: sizeof(wp_adm) 43024 (2264)

M  DpShMCreate: sizeof(tm_adm) 5517056 (27448)

M  DpShMCreate: sizeof(wp_ca_adm) 64000 (64)

M  DpShMCreate: sizeof(appc_ca_adm) 64000 (64)

M  DpCommTableSize: max/headSize/ftSize/tableSize=500/16/584064/584080

M  DpShMCreate: sizeof(comm_adm) 584080 (1144)

M  DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

M  DpShMCreate: sizeof(slock_adm) 0 (296)

M  DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

M  DpShMCreate: sizeof(file_adm) 0 (80)

M  DpShMCreate: sizeof(vmc_adm) 0 (2152)

M  DpShMCreate: sizeof(wall_adm) (41664/42896/64/192)

M  DpShMCreate: sizeof(gw_adm) 48

M  DpShMCreate: sizeof(j2ee_adm) 3952

M  DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000FB60050, size: 6374928)

M  DpShMCreate: allocated sys_adm at 000000000FB60060

M  DpShMCreate: allocated wp_adm_list at 000000000FB63070

M  DpShMCreate: allocated wp_adm at 000000000FB63260

M  DpShMCreate: allocated tm_adm_list at 000000000FB6DA80

M  DpShMCreate: allocated tm_adm at 000000000FB6DAD0

M  DpShMCreate: allocated wp_ca_adm at 00000000100B09E0

M  DpShMCreate: allocated appc_ca_adm at 00000000100C03F0

M  DpShMCreate: allocated comm_adm at 00000000100CFE00

M  DpShMCreate: system runs without slock table

M  DpShMCreate: system runs without file table

M  DpShMCreate: allocated vmc_adm_list at 000000001015E7A0

M  DpShMCreate: system runs without vmc_adm

M  DpShMCreate: allocated gw_adm at 000000001015E850

M  DpShMCreate: allocated j2ee_adm at 000000001015E890

M  DpShMCreate: allocated ca_info at 000000001015F810

M  DpShMCreate: allocated wall_adm at 000000001015F8A0

M  DpCommAttachTable: attached comm table (header=00000000100CFE00/ft=00000000100CFE10)

M  DpRqQInit: use protect_queue / slots_per_queue 0 / 2001 from sys_adm

M  rdisp/queue_size_check_value :  -> on,50,30,40,500,50,500,80

X  EmInit: MmSetImplementation( 2 ).

X  MM global diagnostic options set: 0

X  <ES> client 0 initializing ....

X  <ES> EsILock: use spinlock for locking

X  Using implementation view

X  <EsNT> Using memory model view.

M  <EsNT> Memory Reset disabled as NT default

X  ES initialized.

X  mm.dump: set maximum dump mem to 96 MB

M  DpVmcSetActive: set vmc state DP_VMC_NOT_ACTIVE

M  ThStart: taskhandler started

M  rdisp/thsend_mode : -1 -> 0

M  ThInit: initializing DIA work process W0

M 

M Mon Apr 14 15:11:04 2014

M  ThInit: running on host EGSPL-IDS

M 

M Mon Apr 14 15:11:06 2014

M  calling db_connect ...

B  Loading DB library 'D:\usr\sap\IDS\DVEBMGS00\exe\dbsybslib.dll' ...

B  Library 'D:\usr\sap\IDS\DVEBMGS00\exe\dbsybslib.dll' loaded

B  Version of 'D:\usr\sap\IDS\DVEBMGS00\exe\dbsybslib.dll' is "720.00", patchlevel (0.210)

C  trace file set

C  Callback functions for dynamic profile parameter registered

B  read_con_info_ssfs(): DBSL supports extended connect protocol

B    ==> connect info for default DB will be read from ssfs

C  database is local: connect_timeout: 3

C  Thread ID:6972

C  lib_dbsl 720_REL 02/23/2012 10:32:00

C  Using dynamic link library 'D:\usr\sap\IDS\DVEBMGS00\exe\dbsybslib.dll'

C  dbsybslib.dll patch info

C    SAP patchlevel  0

C    SAP patchno  210

C    Last SYBASE DBSL patchlevel 0

C    Last SYBASE DBSL patchno         210

C    Last SYBASE DBSL patchcomment Sybase ASE R3load fastload is failing (1688468)

C  lpc:(local) connection used on EGSPL-IDS

C 

C Mon Apr 14 15:11:07 2014

C  lpc:(local) connection used on EGSPL-IDS

C 

C Mon Apr 14 15:11:14 2014

C  spid 204 comm rd ODBC

C  spid 207 unc rd ODBC

C  Driver: Adaptive Server Enterprise Driver release: 15.7.0.105

C  Driver full version: Sybase ASE ODBC Driver/15.7.0/ESD#1/P/x86/Windows/drvmain/Build 105/32-bit/Normal/Wed Feb 15 UTC 18:35:16 2012

C  GetServerInfo version: Adaptive Server Enterprise/15.7.0/EBF 20076 SMP ESD#01 Refresh#1/P/X64/Windows Server/aseasap/2926/64-bit/OPT/Thu May 24 01:24:50 2012

C  GetServerInfo release: 15.7.0.012

C  GetServerInfo architecture: unknown

C  GetServerInfo edition: P

C  GetServerInfo byte width: 64 bit

C  DbSlConnect hdl: 0

C  trace file set

B  Connection 0 opened (DBSL handle 0)

M  ThInit: db_connect o.k.

M  ICT: exclude compression: *.zip,*.rar,*.arj,*.z,*.gz,*.tar,*.lzh,*.cab,*.hqx,*.ace,*.jar,*.ear,*.war,*.css,*.pdf,*.gzip,*.uue,*.bz2,*.iso,*.sda,*.sar,*.gif,*.png,*.swc,*.swf

I  MtxInit: 0 0 0

M  SHM_PRES_BUF (addr: 0000000016150050, size: 4400000)

M  SHM_ROLL_AREA (addr: 000007FFDDA80050, size: 268435456)

M  SHM_PAGING_AREA (addr: 0000000016590050, size: 130088960)

M  SHM_ROLL_ADM (addr: 000000001E1B0050, size: 2767448)

M  SHM_PAGING_ADM (addr: 0000000002AA0050, size: 787488)

M  ThCreateNoBuffer allocated 548152 bytes for 1000 entries at 0000000002B80050

M  ThCreateNoBuffer index size: 3000 elems

M  ThCreateVBAdm allocated 30976 bytes (50 server) at 0000000002A10050

X  EmInit: MmSetImplementation( 2 ).

X  MM global diagnostic options set: 0

X  <ES> client 0 initializing ....

X  Using implementation view

X  ES initialized.

X  mm.dump: set maximum dump mem to 96 MB

B 

B Mon Apr 14 15:11:24 2014

B  db_con_shm_ini:  WP_ID = 0, WP_CNT = 19, CON_ID = -1

B 

B Mon Apr 14 15:11:28 2014

B  dbtbxbuf: Buffer TABL  (addr: 0000000024A40160, size: 30000000, end: 00000000266DC4E0)

B  dbtbxbuf: Profile: max_objects = 5000, displace = 1, reorg = 1

B  dbtbxbuf: request_unit = 2000, sync_reload = 5, inval_reload = 5, parallel_penalty = 0

B  dbtbxbuf: protect_shm = 0, force_checks = 0

B  dbtbxbuf: tsize_retry = 14441728

B  dbtbxbuf: obj_entry_size = 208, nt_genkey_entry_size = 28

B  ***LOG BB0=> buffer TABL       started with length 30000000   bytes [dbtbxbuf     16909]

B  dbtbxbuf: Buffer TABLP (addr: 00000000266E0160, size: 10240000, end: 00000000270A4160)

B  dbtbxbuf: Profile: max_objects = 500, displace = 1, reorg = 1

B  dbtbxbuf: request_unit = 2000, sync_reload = 5, inval_reload = 5, parallel_penalty = 50

B  dbtbxbuf: protect_shm = 0, force_checks = 0

B  dbtbxbuf: tsize_retry = 5053184

B  dbtbxbuf: obj_entry_size = 208, nt_genkey_entry_size = 28

B  ***LOG BB0=> buffer TABLP      started with length 10240000   bytes [dbtbxbuf     16909]

B  dbtbxbuf: Reading TBX statistics:

B  dbtbxbuf: 3 object entries precreated

B  dbsync[db_syinit]: shared memory successfully created and initialised, sync_adm_p = 0000000002A20050

B  dbsync[db_syinit]: Buffer synchronisation started with

B    sync_concept      = SEQ_NR

B    sendon            = 0

B    bufreftime        = 120

B    max_gap_wait_time = 60

B    ddlog_del_time    = 60

B    last_counter      = -2147483648

B    oldest_gap        = (2147483647,00000000000000)

B    time_of_last_sync = 20140414151128

B    MySysId           = 'EGSPL-IDS           00'

B  dbexpbuf[EXP_SHB]: Aquired semaphore 35 in db_exp_init(EXP_INIT)

B  Layout of EIBUF buffer shared memory:

B  0: 1 * 4 = 4

B  1: 1 * 424 = 424

B  2: 19 * 40 = 760

B  3: 4001 * 52 = 208052

B  4: 2000 * 256 = 512000

B  5: 4001 * 8 = 32008

B  6: 1 * 200 = 200

B  7: 65 * 8 = 520

B  8: 13438 * 256 = 3440128

B  Tracing = 0, Shm Protection = 0, Force checks = 0, Recovery delay = 500000

B  dbexpbuf: Buffer EIBUF (addr: 00000000270B0170, size: 4194304, end: 00000000274B0170)

B  ***LOG BB0=> buffer EIBUF      started with length 4096k      bytes [dbexpbuf     2312]

B  dbexpbuf[EXP_SHB]: semaphore 35 released in db_exp_init

B  dbexpbuf[EXP_SHM]: Aquired semaphore 56 in db_exp_init(EXP_INIT)

B  Layout of ESM   buffer shared memory:

B  0: 1 * 4 = 4

B  1: 1 * 424 = 424

B  2: 19 * 40 = 760

B  3: 4001 * 52 = 208052

B  4: 2000 * 256 = 512000

B  5: 4001 * 8 = 32008

B  6: 1 * 200 = 200

B  7: 65 * 8 = 520

B  8: 13438 * 256 = 3440128

B  Tracing = 0, Shm Protection = 0, Force checks = 0, Recovery delay = 500000

B  dbexpbuf: Buffer ESM   (addr: 00000000274C0170, size: 4194304, end: 00000000278C0170)

B  ***LOG BB0=> buffer ESM        started with length 4096k      bytes [dbexpbuf     2312]

B  dbexpbuf[EXP_SHM]: semaphore 56 released in db_exp_init

B  dbexpbuf[EXP_CUA]: Aquired semaphore 30 in db_exp_init(EXP_INIT)

B  Layout of CUA   buffer shared memory:

B  0: 1 * 4 = 4

B  1: 1 * 424 = 424

B  2: 19 * 40 = 760

B  3: 3001 * 52 = 156052

B  4: 1500 * 256 = 384000

B  5: 3001 * 8 = 24008

B  6: 1 * 200 = 200

B  7: 193 * 8 = 1544

B  8: 4892 * 512 = 2504704

B  Tracing = 0, Shm Protection = 0, Force checks = 0, Recovery delay = 500000

B  dbexpbuf: Buffer CUA   (addr: 00000000278D0170, size: 3072000, end: 0000000027BBE170)

B  ***LOG BB0=> buffer CUA        started with length 3000k      bytes [dbexpbuf     2312]

B  dbexpbuf[EXP_CUA]: semaphore 30 released in db_exp_init

B  dbexpbuf[EXP_OTR]: Aquired semaphore 55 in db_exp_init(EXP_INIT)

B  Layout of OTR   buffer shared memory:

B  0: 1 * 4 = 4

B  1: 1 * 424 = 424

B  2: 19 * 40 = 760

B  3: 4001 * 52 = 208052

B  4: 2000 * 256 = 512000

B  5: 4001 * 8 = 32008

B  6: 1 * 200 = 200

B  7: 81 * 8 = 648

B  8: 13438 * 256 = 3440128

B  Tracing = 0, Shm Protection = 0, Force checks = 0, Recovery delay = 500000

B  dbexpbuf: Buffer OTR   (addr: 0000000027BC0170, size: 4194304, end: 0000000027FC0170)

B  ***LOG BB0=> buffer OTR        started with length 4096k      bytes [dbexpbuf     2312]

B  dbexpbuf[EXP_OTR]: semaphore 55 released in db_exp_init

B  ***LOG BB0=> buffer CALE       started with length 500000     bytes [dbcalbuf     2211]

B  dbtran INFO (init_connection '<DEFAULT>' [SYBASE:720.00]):

B   max_blocking_factor       =  50,  min_blocking_factor         =   1,

B   max_in_blocking_factor    = 128,  min_in_blocking_factor      =   1,

B   max_union_blocking_factor =  50,  min_union_blocking_factor   =   1,

B   prefer_union_all          =   1,  prefer_join                 =   0,

B   prefer_fix_blocking       =   0,  prefer_in_itab_opt          =   1,

B   convert AVG               =   1,  alias table FUPD            =   0,

B   escape_as_literal         =   0,                                  

B   select *                  =0x0f,  character encoding          = STD / []:X,

B   use_hints                 = abap->1, dbif->0x1, upto->0

M 

M Mon Apr 14 15:11:31 2014

M  SecAudit(rsauinit): Start init of Security Audit Log for first wp.

M  SecAudit(rsauinit): New shared memory created and attached, size = 19488.

M  SecAudit(RsauShmInit): addr of SHM for Audit.... = 0000000002A30050

M  SecAudit(RsauShmInit): addr of RSAUSHM.......... = 0000000002A31050

M  SecAudit(RsauShmInit): addr of RSAUSLOTINFO..... = 0000000002A31660

M  SecAudit(RsauShmInit): addr of RSAUSLOTS........ = 0000000002A31670

M  SecAudit(RsauShmInit): SHM version.............. = 6

M  SecAudit(RsauShmInit): max size of one file..... = 0 KB

M  SecAudit(RsauShmInit): max size of all files.... = 102400 KB

M  SecAudit(RsauShmInit): number of slots available = 90

M  SecAudit(RsauShmInit): number of slots requested = 2

M  SecAudit(RsauShmInit): user selection........... = 0

M  SecAudit(RsauGetCurrentProfile): Init of shared memory completed

M  SecAudit(RsauGetCurrentProfile): Security Audit Log not active

M  SsfSapSecin: automatic application server initialization for SAPSECULIB

N  SsfSapSecin: Looking for PSE in database

N  SsfPseLoad: started...(path=D:\usr\sap\IDS\DVEBMGS00\sec, AS=EGSPL-IDS, instanceid=00)

N  SsfPseLoad: Downloading file D:\usr\sap\IDS\DVEBMGS00\sec (client:    , key: 102635, len: 14851)

N  SsfPseLoadFile: Couldn't open file D:\usr\sap\IDS\DVEBMGS00\sec: Permission denied

N  SsfPseLoad: Downloading file D:\usr\sap\IDS\DVEBMGS00\sec\SAPELEARN200.pse (client:    , key: 172011, len: 1348)

N  SsfPseLoad: Downloading file D:\usr\sap\IDS\DVEBMGS00\sec\SAPSNCS.pse (client:    , key: 025318, len: 804)

N  SsfPseLoad: Downloading file D:\usr\sap\IDS\DVEBMGS00\sec\SAPSSLA.pse (client:    , key: 025401, len: 4367)

N  SsfPseLoad: Downloading file D:\usr\sap\IDS\DVEBMGS00\sec\SAPSSLC.pse (client:    , key: 025427, len: 7806)

N  SsfPseLoad: Downloading file D:\usr\sap\IDS\DVEBMGS00\sec\SAPSSLS.pse (client:    , key: 145420, len: 1840)

N  SsfPseLoad: Downloading file D:\usr\sap\IDS\DVEBMGS00\sec\SAPSYS.pse (client:    , key: SYSPSE, len: 8875)

N  SsfPseLoad: ended (6 of 7 sucessfully loaded, 7 checked...

N  MskiCreateLogonTicketCache: Logon Ticket cache created in shared memory.

N  MskiCreateLogonTicketCache: Logon Ticket cache pointer registered in shared memory.

N  SignInitOnce: Security Context Cache created (max. 2500 entries, 1305600 bytes)

N  No SEC_CONTEXT_COPY records found for deletion

I  MPI: dynamic quotas disabled.

I  MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%

M  rdisp/setactfields_late : -1 -> 0

M  CCMS uses Shared Memory Key 73 for monitoring.

M  CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.

M  CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.

G 

G Mon Apr 14 15:11:32 2014

G  GetWritePermissionForShm( pLocation =  94, pEnforce = 1 )

G 

G Mon Apr 14 15:11:33 2014

G  RelWritePermissionForShm( pLocation = 120, pEnforce = 0 )

G  GetWritePermissionForShm( pLocation =  99, pEnforce = 1 )

G  RelWritePermissionForShm( pLocation = 100, pEnforce = 1 )

S  *** init spool environment

S  TSPEVJOB updates outside critical section: event_update_nocsec = 1

S  initialize debug system

T  Stack direction is downwards.

T  debug control: prepare exclude for printer trace

T  new memory block 0000000028334770

S 

S Mon Apr 14 15:11:34 2014

S  spool kernel/ddic check: Ok

S  using table TSP02FX for frontend printing

S  1 spool work process(es) found

S  frontend print via spool service enabled

S 

S Mon Apr 14 15:11:35 2014

S  printer list size is 150

S  printer type list size is 50

S  queue size (profile)   = 300

S  hostspool list size = 3000

S  option list size is 30

S      found processing queue enabled

S  found spool memory service RSPO-RCLOCKS at 00000000318C00D0

S  doing lock recovery

S  setting server cache root

S  found spool memory service RSPO-SERVERCACHE at 00000000318C06A0

S    using messages for server info

S  size of spec char cache entry: 297032 bytes (timeout 100 sec)

S  size of open spool request entry: 2512 bytes

S  immediate print option for implicitely closed spool requests is disabled

A  ***GENER* Trace switched on ***

A 

A  ---PXA-------------------------------------------

A  PXA INITIALIZATION

A  System page size: 4kb, total admin_size: 22516kb, dir_size: 21724kb.

A  Attached to PXA (address 000007FFEDAB0050, size 300000K, 1 fragments of 277484K )

A  PXA allocated (address 000007FFEDAB0050, size 300000K)

A  abap/pxa = shared protect gen_remote

A  PXA: checking structure sizes: 752|264|16

A  PXA INITIALIZATION FINISHED

A  ---PXA-------------------------------------------

A 

A  ATRA: pfclock execution time = 0

A 

A Mon Apr 14 15:11:36 2014

A  ABAP ShmAdm attached (addr=000007DFF6180000 leng=20955136 end=000007DFF757C000)

A  >> Shm MMADM area (addr=000007DFF6677B80 leng=242240 end=000007DFF66B2DC0)

A  >> Shm MMDAT area (addr=000007DFF66B3000 leng=15503360 end=000007DFF757C000)

A  RFC Destination> destination EGSPL-IDS_IDS_00 host EGSPL-IDS system IDS systnr 0 (EGSPL-IDS_IDS_00)

A  RFC Options> H=EGSPL-IDS,S=00,d=2,

A  RFC FRFC> fallback activ but this is not a central instance.

A   

A  RFC rfc/signon_error_log = -1

A  RFC rfc/dump_connection_info = 0

A  RFC rfc/dump_client_info = 0

A  RFC rfc/cp_convert/ignore_error = 1

A  RFC rfc/cp_convert/conversion_char = 23

A  RFC rfc/wan_compress/threshold = 251

A  RFC rfc/recorder_pcs not set, use defaule value: 2

A  RFC rfc/delta_trc_level not set, use default value: 0

A  RFC rfc/no_uuid_check not set, use default value: 0

H  HTTP> Parameter icf/ssocookie_mandatory set to 0

M  ThrCreateShObjects allocated 39514 bytes at 0000000002A50050

Y  dyWpInit

Y    ztta/dynpro_ara 800000

Y    ztta/cua_ara    500000

Y    ztta/diag_ara   250000

N  SsfSapSecin: getenv(SECUDIR)=="D:\usr\sap\IDS\DVEBMGS00/sec"

N  SsfSapSecin: PSE D:\usr\sap\IDS\DVEBMGS00\sec\SAPSYS.pse found!

N 

N  =================================================

N  === SSF INITIALIZATION:

N  ===...SSF Security Toolkit name SAPSECULIB .

N  ===...SSF library is D:\usr\sap\IDS\DVEBMGS00\exe\sapcrypto.dll .

N  ===...SSF default hash algorithm is SHA1 .

N  ===...SSF default symmetric encryption algorithm is DES-CBC .

N 

N Mon Apr 14 15:11:37 2014

N  ===...SECUDIR="D:\usr\sap\IDS\DVEBMGS00/sec"

N  ===...loading of Security Toolkit successfully completed.

N  ===   SAPCRYPTOLIB  5.5.5C pl32  (Apr  2 2011) MT-safe

N  =================================================

N 

N Mon Apr 14 15:11:54 2014

N  MskiInitLogonTicketCacheHandle: Logon Ticket cache pointer retrieved from shared memory.

N  MskiInitLogonTicketCacheHandle: Workprocess runs with Logon Ticket cache.

M  JrfcVmcRegisterNativesDriver o.k.

W  =================================================

W  === ipl_Init() called

W    ITS Plugin: Path dw_gui

W    ITS Plugin: Description ITS Plugin - ITS rendering DLL

W    ITS Plugin: sizeof(SAP_UC) 2

W    ITS Plugin: Release: 720, [7200.0.210.20020600]

W    ITS Plugin: Int.version, [33]

W    ITS Plugin: Feature set: [29]

W    ===... Calling itsp_Init in external dll ===>

W 

W Mon Apr 14 15:11:55 2014

W  === ipl_Init() returns 0, ITSPE_OK: OK

W  =================================================

N  SignInit: successfully obtained handle for Security Context cache

N  VSI: WP init in ABAP VM completed with rc=0

E 

E Mon Apr 14 15:11:57 2014

E  EnqLockTableAttach2: attach to lock table (size = 33554432)

E  EnqLockTableMapToLocalContext: enque/use_pfclock2 = FALSE

E  EnqId_Initialize: local EnqId initialization o.k.

M 

M Mon Apr 14 15:11:59 2014

M  14.04.2014 09:41:59.598 PID=3820, TID=6972 SapTimer info. v1.119 SynchCount:0 , OwnerPid: 6408, ErrsCount: 0, SapTime-WindowsUtcTime=-7 millisec (max=-7), Nosync=67 sec, SynchsPerDay=0.000000, MaxQpcTimeMinusWindowsTimeMismatch:  +0 millisec, TotalTimeCorrection=+0 millisec, QpcTime-WindowsUtcTime=-7 millisec (*)

A 

A Mon Apr 14 15:12:06 2014

A  UpdateProfile (new settings): off,krn_impl,(no dyn check),(no logging),(no stat err),(local generation),(no commit)

A  UpdateProfile (new exceptions): (tmp_err),(home_err),(local_err)

A  UpdateProfile (new version): 0

A  *GENER* starting remote generation: SAPMSSY2 (requested by W5).

A  *GENER* got lock for program SAPMSSY2.

C  ERROR: -1 in function StartSelect (execute) [line 17173]

C  (208) [42000] [Sybase][ODBC Driver][Adaptive Server Enterprise]D010ENH not found. Specify owne

C  r.objectname or use sp_help to check whether the object exists (sp_help may prod

C  uce lots of output).

C 

C  sql statement is ==> SELECT * FROM "D010ENH" WHERE "IS_ENH" = ? AND "PROGRAMNAME" = ? ORDER BY "IS_EN

C  H" ,"PROGRAMNAME" ,"VERSION" ,"ENHNAME" ,"ID"

C  /* R3::0 T:D010ENH M:000 */

C   /*10

C  */

B  ***LOG BZA=> table D010ENH    does not exist on database R/3        [dbtran       7618]

B  *** ERROR => Buffer loading failed: {fcode=293, rc=32, cnt=0, table='D010ENH'}

[dbrsbuf.c    2220]

B  {root-id=0008A18F03111EE3B0F720B93F2FB0A2}_{conn-id=00000000000000000000000000000000}_0

C  ERROR: -1 in function StartSelect (execute) [line 17173]

C  (208) [42000] [Sybase][ODBC Driver][Adaptive Server Enterprise]D010ENH not found. Specify owne

C  r.objectname or use sp_help to check whether the object exists (sp_help may prod

C  uce lots of output).

C 

C  sql statement is ==> SELECT * FROM "D010ENH" WHERE "IS_ENH" = ? AND "PROGRAMNAME" = ? ORDER BY "IS_EN

C  H" ,"PROGRAMNAME" ,"VERSION" ,"ENHNAME" ,"ID"

C  /* R3::0 T:D010ENH M:000 */

C   /*10

C  */

B  ***LOG BZA=> table D010ENH    does not exist on database R/3        [dbtran       7618]

A  TH VERBOSE LEVEL FULL

A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.

A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.

A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.

A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.

A  ** RABAX: level LEV_RX_HOTSPOT_TRACE entered.

A  ** RABAX: level LEV_RX_HOTSPOT_TRACE completed.

A  ** RABAX: level LEV_RX_SAVE_SHMLOCKS entered.

A  ** RABAX: level LEV_RX_SAVE_SHMLOCKS completed.

A  ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.

A  ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.

A  ** RABAX: level LEV_RX_ROLLBACK entered.

A  *GENER* Performing ROLLBACK.

A  ** RABAX: level LEV_RX_ROLLBACK completed.

A  ** RABAX: level LEV_RX_DB_ALIVE entered.

A  ** RABAX: level LEV_RX_DB_ALIVE completed.

A  ** RABAX: level LEV_RX_HOOKS entered.

A  ** RABAX: level LEV_RX_HOOKS completed.

A  ** RABAX: level LEV_RX_STANDARD entered.

A  ** RABAX: level LEV_RX_STANDARD completed.

A  ** RABAX: level LEV_RX_STOR_VALUES entered.

A  ** RABAX: level LEV_RX_STOR_VALUES completed.

A  ** RABAX: level LEV_RX_C_STACK entered.

A 

A Mon Apr 14 15:12:08 2014

A  ** RABAX: level LEV_RX_C_STACK completed.

A  ** RABAX: level LEV_RX_MEMO_CHECK entered.

A  ** RABAX: level LEV_RX_MEMO_CHECK completed.

A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.

A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.

A  ** RABAX: level LEV_RX_INTERFACES entered.

A  ** RABAX: level LEV_RX_INTERFACES completed.

A  ** RABAX: level LEV_RX_GET_MESS entered.

A  ** RABAX: level LEV_RX_GET_MESS completed.

A  ** RABAX: level LEV_RX_INIT_SNAP entered.

A  ** RABAX: level LEV_RX_INIT_SNAP completed.

A  ** RABAX: level LEV_RX_WRITE_SYSLOG entered.

A  ** RABAX: level LEV_RX_WRITE_SYSLOG completed.

A  ** RABAX: level LEV_RX_WRITE_SNAP_BEG entered.

A  ** RABAX: level LEV_RX_WRITE_SNAP_BEG completed.

A  ** RABAX: level LEV_RX_WRITE_SNAP entered.

A  ** RABAX: level LEV_SN_END completed.

A  ** RABAX: level LEV_RX_WRITE_SNAP_END entered.

A  ** RABAX: level LEV_RX_WRITE_SNAP_END completed.

A  ** RABAX: level LEV_RX_SET_ALERT entered.

A  ** RABAX: level LEV_RX_SET_ALERT completed.

A  ** RABAX: level LEV_RX_COMMIT entered.

A  ** RABAX: level LEV_RX_COMMIT completed.

A  ** RABAX: level LEV_RX_SNAP_SYSLOG entered.

A  ** RABAX: level LEV_RX_SNAP_SYSLOG completed.

A  ** RABAX: level LEV_RX_RESET_PROGS entered.

A  ** RABAX: level LEV_RX_RESET_PROGS completed.

A  ** RABAX: level LEV_RX_STDERR entered.

A  Mon Apr 14 15:12:08 2014

A 

A  Generating ABAP Program SAPMSSY2                                .

A  Source ???????????????????????????????????????? Line 0.

A  Error Code DBIF_RSQL_TABLE_UNKNOWN.

A  Module  $Id: //bas/720_REL/src/krn/gen/scsyenh.c#4 $ SAP.

A  Function performRsqlD010enh Line 1149.

A  ** RABAX: level LEV_RX_STDERR completed.

A  ** RABAX: level LEV_RX_RFC_ERROR entered.

A  ** RABAX: level LEV_RX_RFC_ERROR completed.

A  ** RABAX: level LEV_RX_RFC_CLOSE entered.

A  ** RABAX: level LEV_RX_RFC_CLOSE completed.

A  ** RABAX: level LEV_RX_IMC_ERROR entered.

A 

A Mon Apr 14 15:12:09 2014

A  ** RABAX: level LEV_RX_IMC_ERROR completed.

A  ** RABAX: level LEV_RX_DATASET_CLOSE entered.

A  ** RABAX: level LEV_RX_DATASET_CLOSE completed.

A  ** RABAX: level LEV_RX_ERROR_SAVE entered.

A  ** RABAX: level LEV_RX_ERROR_SAVE completed.

A  ** RABAX: level LEV_RX_ERROR_TPDA entered.

A  ** RABAX: level LEV_RX_ERROR_TPDA completed.

A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.

A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.

A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.

A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.

A  ** RABAX: level LEV_RX_END entered.

A  ** RABAX: level LEV_RX_END completed.

A  ** RABAX: end RX_GOTO_GENEXIT

A 

A Mon Apr 14 15:12:27 2014

A  *GENER* request remote generation: SAPMSSY2.

A 

A Mon Apr 14 15:12:28 2014

A  *GENER* starting inline generation: SAPMSSY2 (reason: compile error during remote generation).

A  *GENER* got lock for program SAPMSSY2.

C 

C Mon Apr 14 15:12:31 2014

C  ERROR: -1 in function StartSelect (execute) [line 17173]

C  (208) [42000] [Sybase][ODBC Driver][Adaptive Server Enterprise]D010ENH not found. Specify owne

C  r.objectname or use sp_help to check whether the object exists (sp_help may prod

C  uce lots of output).

C 

C  sql statement is ==> SELECT * FROM "D010ENH" WHERE "IS_ENH" = ? AND "PROGRAMNAME" = ? ORDER BY "IS_EN

C  H" ,"PROGRAMNAME" ,"VERSION" ,"ENHNAME" ,"ID"

C  /* R3::0 T:D010ENH M:000 */

C   /*10

C  */

B  ***LOG BZA=> table D010ENH    does not exist on database R/3        [dbtran       7618]

A  TH VERBOSE LEVEL FULL

A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.

A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.

A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.

A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.

A  ** RABAX: level LEV_RX_HOTSPOT_TRACE entered.

A  ** RABAX: level LEV_RX_HOTSPOT_TRACE completed.

A  ** RABAX: level LEV_RX_SAVE_SHMLOCKS entered.

A  ** RABAX: level LEV_RX_SAVE_SHMLOCKS completed.

A  ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.

A  ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.

A  ** RABAX: level LEV_RX_ROLLBACK entered.

A  *GENER* Performing ROLLBACK.

A  ** RABAX: level LEV_RX_ROLLBACK completed.

A  ** RABAX: level LEV_RX_DB_ALIVE entered.

A  ** RABAX: level LEV_RX_DB_ALIVE completed.

A  ** RABAX: level LEV_RX_HOOKS entered.

A  ** RABAX: level LEV_RX_HOOKS completed.

A  ** RABAX: level LEV_RX_STANDARD entered.

A  ** RABAX: level LEV_RX_STANDARD completed.

A  ** RABAX: level LEV_RX_STOR_VALUES entered.

A  ** RABAX: level LEV_RX_STOR_VALUES completed.

A  ** RABAX: level LEV_RX_C_STACK entered.

A 

A Mon Apr 14 15:12:33 2014

A  ** RABAX: level LEV_RX_C_STACK completed.

A  ** RABAX: level LEV_RX_MEMO_CHECK entered.

A  ** RABAX: level LEV_RX_MEMO_CHECK completed.

A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.

A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.

A  ** RABAX: level LEV_RX_INTERFACES entered.

A  ** RABAX: level LEV_RX_INTERFACES completed.

A  ** RABAX: level LEV_RX_GET_MESS entered.

A  ** RABAX: level LEV_RX_GET_MESS completed.

A  ** RABAX: level LEV_RX_INIT_SNAP entered.

A  ** RABAX: level LEV_RX_INIT_SNAP completed.

A  ** RABAX: level LEV_RX_WRITE_SYSLOG entered.

A  ** RABAX: level LEV_RX_WRITE_SYSLOG completed.

A  ** RABAX: level LEV_RX_WRITE_SNAP_BEG entered.

A  ** RABAX: level LEV_RX_WRITE_SNAP_BEG completed.

A  ** RABAX: level LEV_RX_WRITE_SNAP entered.

A  ** RABAX: level LEV_SN_END completed.

A  ** RABAX: level LEV_RX_WRITE_SNAP_END entered.

A  ** RABAX: level LEV_RX_WRITE_SNAP_END completed.

A  ** RABAX: level LEV_RX_SET_ALERT entered.

A  ** RABAX: level LEV_RX_SET_ALERT completed.

A  ** RABAX: level LEV_RX_COMMIT entered.

A  ** RABAX: level LEV_RX_COMMIT completed.

A  ** RABAX: level LEV_RX_SNAP_SYSLOG entered.

A  ** RABAX: level LEV_RX_SNAP_SYSLOG completed.

A  ** RABAX: level LEV_RX_RESET_PROGS entered.

A  ** RABAX: level LEV_RX_RESET_PROGS completed.

A  ** RABAX: level LEV_RX_STDERR entered.

A  Mon Apr 14 15:12:33 2014

A 

A  Generating ABAP Program SAPMSSY2                                .

A  Source ???????????????????????????????????????? Line 0.

A  Error Code DBIF_RSQL_TABLE_UNKNOWN.

A  Module  $Id: //bas/720_REL/src/krn/gen/scsyenh.c#4 $ SAP.

A  Function performRsqlD010enh Line 1149.

A  ** RABAX: level LEV_RX_STDERR completed.

A  ** RABAX: level LEV_RX_RFC_ERROR entered.

A  ** RABAX: level LEV_RX_RFC_ERROR completed.

A  ** RABAX: level LEV_RX_RFC_CLOSE entered.

A  ** RABAX: level LEV_RX_RFC_CLOSE completed.

A  ** RABAX: level LEV_RX_IMC_ERROR entered.

A  ** RABAX: level LEV_RX_IMC_ERROR completed.

A  ** RABAX: level LEV_RX_DATASET_CLOSE entered.

A  ** RABAX: level LEV_RX_DATASET_CLOSE completed.

A  ** RABAX: level LEV_RX_ERROR_SAVE entered.

A  ** RABAX: level LEV_RX_ERROR_SAVE completed.

A  ** RABAX: level LEV_RX_ERROR_TPDA entered.

A  ** RABAX: level LEV_RX_ERROR_TPDA completed.

A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.

A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.

A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.

A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.

A  ** RABAX: level LEV_RX_END entered.

A  ** RABAX: level LEV_RX_END completed.

A  ** RABAX: end RX_GOTO_GENEXIT

A  TH VERBOSE LEVEL FULL

A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.

A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.

A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.

A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.

A  ** RABAX: level LEV_RX_HOTSPOT_TRACE entered.

A  ** RABAX: level LEV_RX_HOTSPOT_TRACE completed.

A  ** RABAX: level LEV_RX_SAVE_SHMLOCKS entered.

A  ** RABAX: level LEV_RX_SAVE_SHMLOCKS completed.

A  ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.

A  ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.

A  ** RABAX: level LEV_RX_ROLLBACK entered.

A  ** RABAX: level LEV_RX_ROLLBACK completed.

A  ** RABAX: level LEV_RX_DB_ALIVE entered.

A  ** RABAX: level LEV_RX_DB_ALIVE completed.

A  ** RABAX: level LEV_RX_HOOKS entered.

A  ** RABAX: level LEV_RX_HOOKS completed.

A  ** RABAX: level LEV_RX_STANDARD entered.

A  ** RABAX: level LEV_RX_STANDARD completed.

A  ** RABAX: level LEV_RX_STOR_VALUES entered.

A  ** RABAX: level LEV_RX_STOR_VALUES completed.

A  ** RABAX: level LEV_RX_C_STACK entered.

A  ** RABAX: level LEV_RX_C_STACK completed.

A  ** RABAX: level LEV_RX_MEMO_CHECK entered.

A  ** RABAX: level LEV_RX_MEMO_CHECK completed.

A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.

A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.

A  ** RABAX: level LEV_RX_INTERFACES entered.

A  ** RABAX: level LEV_RX_INTERFACES completed.

A  ** RABAX: level LEV_RX_GET_MESS entered.

A  ** RABAX: level LEV_RX_GET_MESS completed.

A  ** RABAX: level LEV_RX_INIT_SNAP entered.

A  ** RABAX: level LEV_RX_INIT_SNAP completed.

A  ** RABAX: level LEV_RX_WRITE_SYSLOG entered.

A  ** RABAX: level LEV_RX_WRITE_SYSLOG completed.

A  ** RABAX: level LEV_RX_WRITE_SNAP_BEG entered.

A  ** RABAX: level LEV_RX_WRITE_SNAP_BEG completed.

A  ** RABAX: level LEV_RX_WRITE_SNAP entered.

A  ** RABAX: level LEV_RX_WRITE_SNAP completed.

A  ** RABAX: level LEV_RX_WRITE_SNAP_END entered.

A  ** RABAX: level LEV_RX_WRITE_SNAP_END completed.

A  ** RABAX: level LEV_RX_SET_ALERT entered.

A  ** RABAX: level LEV_RX_SET_ALERT completed.

A  ** RABAX: level LEV_RX_COMMIT entered.

A  ** RABAX: level LEV_RX_COMMIT completed.

A  ** RABAX: level LEV_RX_SNAP_SYSLOG entered.

A  ** RABAX: level LEV_RX_SNAP_SYSLOG completed.

A  ** RABAX: level LEV_RX_RESET_PROGS entered.

A  ** RABAX: level LEV_RX_RESET_PROGS completed.

A  ** RABAX: level LEV_RX_STDERR entered.

A  ** RABAX: level LEV_RX_STDERR completed.

A  ** RABAX: level LEV_RX_RFC_ERROR entered.

A  ** RABAX: level LEV_RX_RFC_ERROR completed.

A  ** RABAX: level LEV_RX_RFC_CLOSE entered.

A  ** RABAX: level LEV_RX_RFC_CLOSE completed.

A  ** RABAX: level LEV_RX_IMC_ERROR entered.

A  ** RABAX: level LEV_RX_IMC_ERROR completed.

A  ** RABAX: level LEV_RX_DATASET_CLOSE entered.

A  ** RABAX: level LEV_RX_DATASET_CLOSE completed.

A  ** RABAX: level LEV_RX_ERROR_SAVE entered.

A  ** RABAX: level LEV_RX_ERROR_SAVE completed.

A  ** RABAX: level LEV_RX_ERROR_TPDA entered.

A  ** RABAX: level LEV_RX_ERROR_TPDA completed.

A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.

A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.

A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.

A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.

A  ** RABAX: level LEV_RX_END entered.

A  ** RABAX: level LEV_RX_END completed.

A  ** RABAX: end no http/smtp

A  ** RABAX: end RX_BTCHLOG|RX_VBLOG

E 

E Mon Apr 14 15:13:07 2014

E  Enqueue Info: enque/use_pfclock2 = FALSE

E  Enqueue Info: row condense enabled

M 

M Mon Apr 14 16:04:58 2014

M  in_ThErrHandle: 1

M Mon Apr 14 16:04:59 2014

M  ThIErrHandle: new stat of W0 is WP_SHUTDOWN   

M  ThIErrHandle: I'm during shutdown

M  PfStatDisconnect: disconnect statistics

M  ThIErrHandle: entering ThSetStatError

M Mon Apr 14 16:05:00 2014

M  Pipe read request: 2 anz: 64

C Mon Apr 14 16:05:01 2014

C  SybBreak

B  db_sqlbreak() = 15

M  *** WARNING => ThCallDbBreak: db_sqlbreak failed (16388), caller=ThIErrHandle

M  ThIErrHandle: don't try rollback again

M  ThShutDownServer: shutdown server

M  Signal handling in an APC of the main thread (signal SIGINT)

M Mon Apr 14 16:05:02 2014

M  PfWriteIntoFile: shared buffer is empty.

M  ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)

M  Entering ThReadDetachMode

M 

M Mon Apr 14 16:05:04 2014

M  call ThrShutDown (1)...

B 

B Mon Apr 14 16:05:05 2014

B  Disconnecting from ALL connections:

B  Wp  Hdl ConName          ConId     ConState     TX  BC  HC  PRM RCT FRC TIM MAX OPT Date     Time   DBHost           Program                                

B  000 000 R/3              000000000 INACTIVE     NO  NO  NO  YES NO  NO  000 255 255 20140414 151106 EGSPL-IDS                                               

C  DbSlDisconnect hdl: 0

B 

B Mon Apr 14 16:05:28 2014

B  Disconnected from connection 0

B  statistics db_con_commit (com_total=20, com_tx=5)

B  statistics db_con_rollback (roll_total=4, roll_tx=4)

M  ***LOG Q02=> wp_halt, WPStop (Workp. 0 3820) [dpnttool.c   339]

I have ASE backup every day and log backup every hour. then I get the backup file like:

....

-rw-r--r--  1 sybase sybase 5332286485 Apr 12 20:31 mydb.dmp

-rw-r--r--  1 sybase sybase      18048 Apr 12 21:01 my_log_20140412_02.dmp

-rw-r--r--  1 sybase sybase     229836 Apr 12 22:01 my_log_20140412_03.dmp

-rw-r--r--  1 sybase sybase     173399 Apr 12 23:01 my_log_20140412_04.dmp

-rw-r--r--  1 sybase sybase     408999 Apr 13 00:01 my_log_20140412_05.dmp

.....

then I try to restore it on another box. firstly, restore mydb.dmp and it is fine with message:

Backup Server: 3.42.1.1: LOAD is complete (database mydb).

Caution:  You have set up this database to include space on disk 19 for both

data and the transaction log.  This can make recovery impossible if that disk

fails.

Caution:  You have set up this database to include space on disk 20 for both

data and the transaction log.  This can make recovery impossible if that disk

fails.

Started estimating recovery log boundaries for database 'mydb'.

Database 'mydb', checkpoint=(11742880, 11), first=(115975859872, 11),

last=(11742913, 5).

Completed estimating recovery log boundaries for database 'mydb'.

Started ANALYSIS pass for database 'mydb'.

Completed ANALYSIS pass for database 'mydb'.

Started REDO pass for database 'mydb'. The total number of log records to

process is 471.

Redo pass of recovery has processed 30 committed and 5 aborted transactions.

Completed REDO pass for database 'mydb'.

Use the ONLINE DATABASE command to bring this database online; SQL Server will

not bring it online automatically.

then I try to restore next log backup my_log_20140412_02.dmp and got message:

Backup Server session id is:  23.  Use this value when executing the

'sp_volchanged' system stored procedure after fulfilling any volume change

request from the Backup Server.

Backup Server: 4.132.1.1: Attempting to open byte stream device:

'compress::1::/home/mydump/my_log_20140412_02.dmp::00'

Backup Server: 6.28.1.1: Dumpfile name 'mydb14102135A2' section number 1

mounted on byte stream

'compress::1::/home/mydump/my_log_20140412_02.dmp::00'

Msg 4305, Level 16, State 1:

Server 'MYSYB', Line 1:

Specified file 'dump device' is out of sequence. Current time stamp is Apr 12

2014  6:01:01:433PM while dump was from Apr 12 2014  9:19:54:890PM.

Not sure why. It said out of sequence. but  the backup sequence is right. after mydb.dmp, the next backup is my_log_20140412_02.dmp. why have this error? how to resolve it?

want to stop ASE backup server. One way is: use showserver find out pid, then kill it.

Any other way to stop it wiitout any problem?

If restore ase db, all data cache bound to the objects in the database will be cleaned?

Hi All,

I am planning to install SAP on Linux (SUSE) and ASE (Sybase) DB.

Can you please share the installation doc/guide for same.

Thanks in Advance,

Vinod

I reboot ASE 12.5 on CentOS by reboot command.

After that, I then want to start Sybase ASE by the script like RUN_ASEServer, but got the error:

....

00:00000:00000:2014/04/02 15:20:59.29 kernel  os_create_region: shmget(0xf402f68e): No space left on device                                                                                                                                 

00:00000:00000:2014/04/02 15:20:59.29 kernel  kbcreate: couldn't create kernel region.

00:00000:00000:2014/04/02 15:20:59.29 kernel  kistartup: could not create shared memory

Not sure why.

How to resolve it?

I have a table which is about 2G size. the lock type on this table is set as AllPage.  I think this cause performance issue when issue select query, many SH lock applied. I try to change the lock type to datarow, which should have no lock when issue select as document indicated.

but when I try it with DBArtisan, it took longtime and never end. Then I stop the app and connect it again. I found the lock type do change it to datarow. but there is a new table name like mytab_3309ac22 created.

then I try to change lock type again on other table and got following info:

You can not run Alter Table Lock in this database because the 'select into/bulkcopy' option is off.

Looks like dboption changed. So want to know if this is safe for data when change lock type? how to ensure it is done properly?

Good afternoon, colleagues.

Tell me what there is common measures to check the Sybase database for consistency? I of course mean dbcc commands. I would be happy with any links and if you share your personal experience in this matter.

Hi Experts,

I've installed ECC6 Ehp7 on Sybase 15.7.0.101 and Windows 2008 R2. Im facing an error when run DB02 related to page cannot be displayed.

I actived ICF services in the ICF three.

I don't know how to fix it and cannot find any documents that describe this error, also I need please to know what others post-installations actions are required for Sybase.

Sorry but Im new installing SAP on Sybase.

Thanks at lot.

JuanManuel