Hi there,

is there a way to point to a sql.ini (or other interface file) on another server?

The idea is to create a central sql.ini where all servers and clients look at.

I am aware of the consequences (singel point of failure, no freedom for clients etc) but maintaining hundreds of sql.ini/dns/odbc files is not why i became a DBA ;-).

I'm not looking for a push mechanism....(autocopy to servers and clients)

Thanks in advance for your input,

Harry Splinter

I been manually pulling replication-based synchronization monitoring data from Sybase Control Center (Monitoring - Replication - History). Is there anyway to retrieve the replication history automatically by running script or command prompt?

Can help me someone with the following issues?

We are testing the database inmemory option for SAP ASE, the purpose is to reduce the execution time of the batch process, but we have had the following problems:

When we have enabled full dml_logging the log is consumed very quickly and we visualize LOG SUSPEND message therefore we have placed this dml_logging minimal

Could this help us optimize the runtime on a batch process?

That we could have disadvantages when using this option?

Thanks in Advance

Good day,

I have a process which after some minutes starts blocking users . The output shows for command "dbcc", status "lock sleep" and the tx name is "rs_logexec". ( no Rep Server used )

If sp_procxmode  in not used,  are there any other known reasons  for this to happen?

It's an old ASE 12.5.3 on Solaris 9

Thank you

Regards

Jose

For the server to have the correct statistics of the indexes on the temporary table when should the indexes be created?

a.    When the table is created and there is no data.

b.    When the data is inserted in the table.

c.    We cannot create an index on a temporary table

d.    Anywhere before the usage of the table.

Hi, I'm installing a new ASE 16 server on Windows 2008 R2 SP1, after the server has been set up and started, there is a system process which seems stuck on "Maintenance Token" as the cmd. When I try and shutdown the server, it waits indefinitely for this process to stop. The only way I can shutdown is with nowait option. Why is this process stuck on "Maintenance Token"?

Any help greatly appreciated!

What's new in ASE Cockpit?

First, what is "ASE Cockpit"?

We introduced ASE Cockpit in the previous blog in this series, here: ASE Cockpit (in lieu of SCC 3 for ASE).

ASE Cockpit is planned to be a new User Interface (or Tooling) component for ASE, and is planned to be released in 2015. The User Interface (or Tooling) of ASE Cockpit will manage ASE. ASE Cockpit is targeted as an essential companion tool for a Database Administrator (DBA) of ASE.

So, what's new in "ASE Cockpit"?

ASE Cockpit will have all the monitoring and capabilities of SAP Control Center (SCC) 3 for its ASE, plus the support for the following new features/capabilities in upcoming ASE. Due to ASE Cockpit being a superset of SCC 3 in managing its ASE, ASE Cockpit will replace SCC 3 in the packaging of its upcoming ASE release.

1. ASE Cockpit supports more platforms than SCC 3 for ASE:
   • Added platforms: AIX and HPIA
2. ASE Cockpit supports new ASE features:
   1. Always-on Option (HA/DR)
   2. Workload Analyzer Option
   3. Data Store and Access Management (DSAM)
3. Other benefits of ASE Cockpit:
   1. Easier installation
   2. New look
   3. Simpler Alerting
   4. Localization
      

Now let's expand on each of the above new capabilities of ASE Cockpit.

+++

Increase in Platform support, and Easier installation

(1 & 3.i)

ASE Cockpit has to support more platforms than SCC 3 because ASE Cockpit is co-located with the ASE and has to support all platforms ASE supports. ASE platform support information is typically included in the product documentation. In contrast to ASE Cockpit, SCC 3 did not have to be located on the same host as the ASE.

But, why is this new capability or attribute of ASE Cockpit significant? This capability is significant not necessarily because a few more platforms were added, but because ASE Cockpit now co-locates with its deployed ASE. Co-locating the ASE Cockpit simplifies the installation and configuration needed before you can manage your ASE with it.

More importantly, this co-location and simplification of ASE Cockpit is important because this is expected to meet a key request/requirement from our ASE customers. As a quick flashback, the inputs and feedback we received from our ASE customers was to further simplify the SCC 3 installation. And this co-location of ASE Cockpit essentially simplifies the installation steps (vis-a-vis the SCC 3 installation steps).

The almost automated install, registering, startup, etc., by the co-locating of ASE Cockpit with ASE offers a significant progress in ease-of-use and simplification.

+++

Always-on Option (HA/DR)

(2.i)

New for the upcoming ASE release in 2015 is its "Always-on Option". The Always-on Option of ASE consists of components for High Availability (HA) as well as for Disaster Recovery (DR) implementation. True to its low TCO advantage and commitment of simplifying, with its release ASE will be combining HA as well as DR into one package.

Notably, the key point is that: ASE Cockpit will provide the User Interface (UI) coverage for the management of the ASE Always-on (HADR) environment.

Workload Analyzer Option

(2.ii)

This new option for the upcoming ASE release will enable Workload Capture and Replay of production workload non-disruptively, and utilize the data to diagnose problems, and to understand and manage configuration changes proactively. It will aid in:

• Identifying problematic queries
• Investigating client activities
• Measure impact from configuration changes
• Evaluate upgrade options and new features to understand their benefits
• Evaluate migration options by anticipating upgrade/migration benefits

ASE Cockpit will be the UI for this new ASE feature.

Data Store and Access Management (DSAM)

(2.iii)

The new DSAM new in the upcoming release of ASE can enable you to maximize the value of existing storage subsystem by taking into account the varying access frequencies over a period of time, the value of data during the complete data lifecycle, and savings through placing data on the most efficient devices. It will help in:

• Data usage monitoring
• Moving data to faster devices, or to archive devices, based on data access activity
• Enhance performance by keeping active data on high performance storage
• Reduce costs (enabling more effective use of storage assets)

The UI for DSAM feature will be in ASE Cockpit.

+++

The new look and feel

(3.i)

ASE Cockpit re-uses various components of its predecessor SCC 3, but with a refreshed UI template and a simplified top-level navigation.

ASE Cockpit will use a UI template consistent with the UI standards at SAP, and will make ASE Cockpit look similar to the IQ Cockpit and ESP Cockpit. (Note that ASE Cockpit will emulate the UI5 UX3 standard at SAP on its Adobe Flash UI, and not use Fiori HTML5 standards used by HANA Cockpit.)

In addition, ASE Cockpit will use the fuller real-estate of the browser compared to the windows-in-a-window layout of SCC 3.

And finally, the top-menu (Application and/or File menus) and top-level toolbar of SCC 3 are simplified with the following three tabs instead:

1. MONITOR - View the real-time and historical charts
2. EXPLORE - View database components and entities, and manage them through provided admin functions
3. ALERT - Manage the alerting setup, configurations and preferences
   

Simpler Alerting

(3.ii)

ASE Cockpit simplifies Alerting for its ASE to the ease of selecting a checkbox. Where SCC 3 required you to define/setup the name, preferences and thresholds of an Alert before you could apply it, ASE Cockpit simplifies this internally to set predefined thresholds that will trigger its alerts. This simplification gets you started on basic Alerting right after you install ASE. You can then modify these preset threshold values in the "Alert" tab.

ASE Cockpit uses Key Performance Areas (KPAs) as the metrics and/or aggregates for its alerts. These KPAs in ASE Cockpit are a replacement to the Key Performance Indicators (KPIs) in SCC 3. (In other words, the KPIs of SCC 3 have been reclassified in ASE Cockpit as KPAs.) These KPAs are classified into four categories: Availability, Performance, Capacity and Alerts (acronym "APCA"). ASE Cockpit internally has "Collection jobs" scheduled and run to collect these KPA statuses.

Localization support

(3.iii)

ASE Cockpit debut release will support localization in Japanese and Simplified Chinese. Note that, in contrast, SCC 3 did not support Localization. (ASE Cockpit, and SCC 3, are internationalized.)

***

Jump to a sub-topic in this blog:

***

Coming next ... "Which DBA Tool to use with ASE, and when?"

***

Appendix: Screenshots

(Click on a screenshot to see higher resolution)

• Login screens

• ASE Cockpit

• SCC3

• Look and feel

• ASE Cockpit

• SCC3

• Alert setup

• ASE Cockpit

• SCC3

Hi Everybody,

I have  2 ASE companion servers running on a symmetric configuration and I need to configure a proxy db on my primary companion server that points to third ASE server

What are the considerations, that I need to have? and what steps I need to follow in order to obtain this configuration?

Best Regards,

Jairo

With the introduction of ASE Edge Edition, I was wondering if anyone knows what the final version of ASE Small Business Edition (SBE) will be?  Also, what is the latest SBE version?

Any help appreciated.

For the past few months we have had an error like the one below appear in our ASE log. The error initially occurred once a week or so but in the last few weeks it has started happening almost daily.

00:03:00000:00078:2015/06/15 08:27:18.38 kernel  Address 0x0x0000000000b7c67b (fm_unlink_frame+0x2b), siginfo (code, address) = (1, 0x0x00000000deadbabe)

00:03:00000:00078:2015/06/15 08:27:18.39 kernel  ************************************

00:03:00000:00078:2015/06/15 08:27:18.39 kernel  SQL causing error :

00:03:00000:00078:2015/06/15 08:27:18.39 kernel  ************************************

00:03:00000:00078:2015/06/15 08:27:18.39 server  SQL Text:

00:03:00000:00078:2015/06/15 08:27:18.39 kernel  curdb = 1 tempdb = 0 pstat = 0x10000 p2stat = 0x141000

00:03:00000:00078:2015/06/15 08:27:18.39 kernel  p3stat = 0x900 p4stat = 0x0 p5stat = 0x8 p6stat = 0x10 p7stat = 0x10000

00:03:00000:00078:2015/06/15 08:27:18.39 kernel  lasterror = 0 preverror = 0 transtate = 1

00:03:00000:00078:2015/06/15 08:27:18.39 kernel  curcmd = 0 program = PHP 5

00:03:00000:00078:2015/06/15 08:27:18.39 kernel  extended error information: hostname: xxx.xxx.xxx login: lGbReportXXXXXXXX

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  pc: 0x000000000176740f pcstkwalk+0x30()

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  pc: 0x0000000001767205 ucstkgentrace+0x1a5()

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  pc: 0x0000000001706771 ucbacktrace+0x43()

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  pc: 0x000000000074360e terminate_process+0xd5e()

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  pc: 0x0000000001733d03 kisignal+0x3b3()

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  pc: 0x0000000000b7c67b fm_unlink_frame+0x2b()

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  pc: 0x0000000000b7c346 fm_free_frame+0x16()

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  pc: 0x0000000000b7c3c8 fm_free_list+0x18()

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  [Handler pc: 0x0x000000000153acde hdl_backout_msg installed by the following function:-]

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  pc: 0x0000000000b68d56 db__create_sysusages_map+0x126()

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  pc: 0x0000000000b66cf9 db_fill+0x159()

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  [Handler pc: 0x0x000000000153acde hdl_backout_msg installed by the following function:-]

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  pc: 0x0000000000b6bdfb dbt(float, int, long, long)+0x16b()

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  pc: 0x00000000019b0a70 dbt_get+0x440()

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  pc: 0x0000000000b6dd4f dbt_get_with_statuscheck+0xf()

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  pc: 0x0000000000b62f4a usedb_cmd+0x7a()

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  [Handler pc: 0x0x00000000010b644f hdl__login installed by the following function:-]

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  pc: 0x000000000074c7d4 login+0x734()

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  [Handler pc: 0x0x0000000000d4e930 ut_handle installed by the following function:-]

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  pc: 0x000000000191c52f conn_hdlr+0x51f()

00:03:00000:00078:2015/06/15 08:27:18.40 kernel  end of stack trace, spid 78, kpid 951451747, suid 1621

After this error occurs, MAINTENANCE TOKEN processes start appearing on the server. More and more of them start, never finish, and they cannot be killed. Dataserver performance eventually degrades - the only solution is to perform a shutdown with nowait and restart the dataserver.

The error is usually like the above, but occasionally has errors like this related to memory:

00:03:00000:00127:2015/06/11 20:43:18.95 server  Error: 715, Severity: 20, State: 2

00:03:00000:00127:2015/06/11 20:43:18.95 server  Unable to locate a procedure cache memory control descriptor for memory '0x0x176731800' in the global list.

00:03:00000:00127:2015/06/11 20:43:18.95 server  Error: 715, Severity: 20, State: 2

00:03:00000:00127:2015/06/11 20:43:18.95 server  Unable to locate a procedure cache memory control descriptor for memory '0x0x16ec53000' in the global list.

00:01:00000:00127:2015/06/11 20:43:19.13 server  Error: 715, Severity: 20, State: 2

00:01:00000:00127:2015/06/11 20:43:19.13 server  Unable to locate a procedure cache memory control descriptor for memory '0x0x1a10ec800' in the global list.

00:01:00000:00127:2015/06/11 20:43:19.13 server  Error: 715, Severity: 20, State: 2

00:01:00000:00127:2015/06/11 20:43:19.13 server  Unable to locate a procedure cache memory control descriptor for memory '0x0x1b12c7000' in the global list.

00:01:00000:00127:2015/06/11 20:43:19.13 server  Error: 715, Severity: 20, State: 2

00:01:00000:00127:2015/06/11 20:43:19.13 server  Unable to locate a procedure cache memory control descriptor for memory '0x0x177752000' in the global list.

00:01:00000:00127:2015/06/11 20:43:19.13 server  Error: 715, Severity: 20, State: 2

00:01:00000:00127:2015/06/11 20:43:19.13 server  Unable to locate a procedure cache memory control descriptor for memory '0x0x18fe13000' in the global list.

00:01:00000:00127:2015/06/11 20:43:19.13 server  Error: 715, Severity: 20, State: 2

00:01:00000:00127:2015/06/11 20:43:19.13 server  Unable to locate a procedure cache memory control descriptor for memory '0x0x16bfe9000' in the global list.

00:01:00000:00127:2015/06/11 20:43:19.13 server  Error: 714, Severity: 20, State: 2

00:01:00000:00127:2015/06/11 20:43:19.13 server  Unable to locate a procedure cache memory control descriptor for memory '0x0x1b5c22800' allocated by process 127.

00:01:00000:00127:2015/06/11 20:43:19.13 server  Error: 715, Severity: 20, State: 2

00:01:00000:00127:2015/06/11 20:43:19.13 server  Unable to locate a procedure cache memory control descriptor for memory '0x0x1b4a92000' in the global list.

00:01:00000:00127:2015/06/11 20:43:19.13 server  Error: 715, Severity: 20, State: 2

00:01:00000:00127:2015/06/11 20:43:19.13 server  Unable to locate a procedure cache memory control descriptor for memory '0x0x1b64bd800' in the global list.

00:01:00000:00127:2015/06/11 20:43:19.13 server  Error: 715, Severity: 20, State: 2

00:01:00000:00127:2015/06/11 20:43:19.13 server  Unable to locate a procedure cache memory control descriptor for memory '0x0x1b64df000' in the global list.

00:01:00000:00127:2015/06/11 20:43:19.13 server  Error: 714, Severity: 20, State: 2

00:01:00000:00127:2015/06/11 20:43:19.13 server  Unable to locate a procedure cache memory control descriptor for memory '0x0x1b63bb560' allocated by process 127.

00:01:00000:00127:2015/06/11 20:43:19.13 server  (mem_freepages) Diagnostics for error 707 state 8: addr=0x0x1b63bb560 mem free failed retcode=-3 pgcount=0

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  pc: 0x000000000176740f pcstkwalk+0x30()

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  pc: 0x0000000001767205 ucstkgentrace+0x1a5()

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  pc: 0x0000000001706771 ucbacktrace+0x43()

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  pc: 0x00000000019c8715 mem_freepages+0x205()

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  pc: 0x0000000000b868a8 free_memchunk+0x98()

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  pc: 0x0000000000b7c390 fm_free_frame+0x60()

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  pc: 0x0000000000b7c3c8 fm_free_list+0x18()

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  [Handler pc: 0x0x000000000153acde hdl_backout_msg installed by the following function:-]

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  pc: 0x0000000000b68d56 db__create_sysusages_map+0x126()

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  pc: 0x0000000000b66cf9 db_fill+0x159()

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  [Handler pc: 0x0x000000000153acde hdl_backout_msg installed by the following function:-]

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  pc: 0x0000000000b6bdfb dbt(float, int, long, long)+0x16b()

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  pc: 0x00000000019b0a70 dbt_get+0x440()

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  pc: 0x0000000000b6dd4f dbt_get_with_statuscheck+0xf()

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  pc: 0x0000000000b62f4a usedb_cmd+0x7a()

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  [Handler pc: 0x0x00000000010b644f hdl__login installed by the following function:-]

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  pc: 0x000000000074c7d4 login+0x734()

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  [Handler pc: 0x0x0000000000d4e930 ut_handle installed by the following function:-]

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  pc: 0x000000000191c52f conn_hdlr+0x51f()

00:01:00000:00127:2015/06/11 20:43:19.13 kernel  end of stack trace, spid 127, kpid 1491992657, suid 1853

00:01:00000:00127:2015/06/11 20:43:19.13 server  Error: 707, Severity: 20, State: 8

00:01:00000:00127:2015/06/11 20:43:19.13 server  System error detected during attempt to free memory at address 0x1b63bb560. Please consult the ASE error log for more details.

00:01:00000:00127:2015/06/11 20:43:20.03 server  WARNING: memory usage in procedure headers (2)

does not match memory usage count in Pss (4294965921) for server process id 127.

00:01:00000:00127:2015/06/11 20:43:20.33 server  Error: 715, Severity: 20, State: 2

We have tried tweaking the server settings in this post SAP Sybase Forums - ASE - Administration - Maintenance Token and high CPU but it has not helped. We have a support license for one of our machines, unfortunately it it not for this machine. Our other servers perform similar work and have similar hardware specifications but this server is the only one with a problem. The login lGbReportXXXXXXXX is one login of many and it changes each time - the issue does not appear to be related to a single database or login.

The server version is:

Adaptive Server Enterprise/15.5/EBF 18661 SMP ESD#4/P/x86_64/Enterprise Linux/a

         sear155/2545/64-bit/FBO/Thu Jun 16 06:45:54 2011

Any idea what is causing these errors and how we can fix the issue?

Any help appreciated. Cheers

SAP Sybase Database ASE Installation steps on Linux

Summary :-

This document contains the steps that how to install SAP Sybase ASE on Linux. I have gone through many SAP SCN link and created this documents.

About SAP ASE :-

SAP Adaptive Server® Enterprise 15.7 is a high-performance relational database management system for mission-critical, data-intensive environments.It ensures highest operational efficiency and throughput on a broad range of platforms.

SAP ASE Sybase recommends that you use the GUI wizard to install Adaptive Server.

Table of Contents :-

1) SAP ASE Sysbase Architecture

2) Hardware Requirements

3) Software & Installation

1) SAP  ASE 15.7 Sybase Architecture

ASE 15.7 – Virtual Server Architecture (VSA)

2) Hardware Requirements & Operating system

Required libraries for Linux

• openmotif-2.3.1-2.el5

• libXp-1.0.0-8.1.el5

• libXt-1.0.2-3.1.fc6

• libXtst-1.0.1-3.1

• libXi-1.6.1-1

• libXmu-1.0.2-5

• libXext-1.0.1-2.1

• libSM-1.0.1-3.1

• libICE-1.0.1-2.1

• libX11-1.0.3-9.el

Required X/Motif-related RPM package

manager files

• libXtst-devel

• libXi-devel

• openmotif-devel

• libXmu-devel

• libXt-devel

• libXext-devel

• libXp-devel

• libX11-devel

• libSM-devel

• libICE-devel

These files should be compatible with RHEL5.3 or later.

In addition, there is a known OS kernel bug in scheduling threads in RHEL 6.0 that has been

fixed in RHEL 6.1; for this reason, Sybase recommends that you use 6.1.

Linux 64-bit x64 system memory requirements are:

• MinimumRAM required for AdaptiveServer, with defaultstack size, packetsize, and user

log cache size – 127 MB

• Minimum RAM per additional user – approximately 324KB

• Default user stack size – 128KB

3) Software &  Installation

Downloaded the product from SPDC or SAP Service Marketplace, go to the directory where you extracted the

installation image and start the installer:

Note : Before you can install a 64-bit Adaptive Server version 15.7 ESD #2 to a Red Hat Enterprise

Linux 6.x x86_64, install the 32-bit GNU C Libraries package (glibc-2.xxx.xx.el6.i686.rpm). Each operating system has a default maximum shared-memory segment. Configure your operating system to allow the allocation of a shared-memory segment at least as large as the maximum memory value.

step 1

Log into OS level in Linux and use x-manager or other tool to launch the GUI wizard

Once you extracted the file which you  are extracted the got to the directories   and execute the below command

./setup.bin

1. Choose as the installation directory

/sysdbase

2. ‘Full’ installation then click ' Next'

3. Select license  then click 'Next'

4. Accept the license for your location  and then Click ' Next'

5. Review the Pre-Installation Summary – All components will be installed 'Next'

6. Select to configure ASE and its companion servers, plus Sybase Control Center and then Click 'Next'

7. The ASE Server name will default to the machine's network node name - leave this asa default. Then click 'Next'

8. Set network port to 5000 (Windows default)

9. Leave Language, Character Set and Sort Order at default (see Notes)

10. Do NOT select to optimize ASE

11. Select to Create Sample databases

12. Click OK for the following message. We want 4k or higher page size

13. Ensure all devices are under the $SYBASE\data directory and default sizes. Then Click ' Next'

14. Keep Backup Server default name and port (5001) and the click ' Next'

15. Keep XP server name and port (5002) and then click 'Next'

16. Keep Job Scheduler agent name and port(4900) and then click 'Next'

17. Leave ‘sa’ as self management user and then click 'Next'

18. Only configure UDP Adapter for discovery services and then click 'Next'

19. Leave default ports (8282, 8283) for SCC  and then click 'Next'

20. Leave RMI service port at 9999 and then Click 'Next'

21. Set sccadmin password and uafadmin

password to ‘sybase’ and then click 'Next'

22. Select ‘Yes’ to start SCC as a service and then click 'Next'

23. Review final installation summary screen

24. Installation and configuration starts – ASE and XP server first, then BS, JS_AGENT and SCC.

ASE may be stopped and restarted several times during this process

All the steps are done!

Unable to connect to database. xxx.db.ConnectionException: DBServer::GetConnection: mscorlib: Could not load file or assembly 'Sybase.AdoNet4.AseClient, Version=4.157.1300.0, Culture=neutral' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040): at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection) at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at

I am getting the above error when i use the new 64 bit dll. Can you please suggest from stack trace what could be the error?

Since 15.0.x ASE comes with handy PC MDAs - monProcedureCacheMemoryUsage and monProcedureCacheModuleUsage.  Both are "essential" in sizing the PC correctly - and analyzing PC behavior for your application & ASE.  There counters are very nice but... over time they become user-un-friendly.

Both counters are not absolute point-in-time sample values but rather grow over time.  But if they grow - what do they show?

• Active (for ModuleUsage) must show "Number of memory pages (2K) currently allocated to this module".
• HWM show "The maximum number of memory pages allocated since the server was started."

There may be further broken down into sub-allocators.

You'd expect Active to indicate the sample value from the point-of-time of inspection and HWM to indicate the number of memory pages since the startup (i.e. relative to the DaysRunning from the monState).  Yet, both behave in the same cumulative manner and both yield useless values if divided into daily portions and compared to say monitorconfig.   The same applies to the reuse values packed into these tables.

Anyone tried to make sense of these values?   They are essential in configuring PC on the one hand but accumulate over time on the other (and exceed PC size in hundreds of % + are marked as indicator&1).   What do these in fact display?  How do they relate to monitorconfig?  When you restart ASE (or play with these on your private ASE) the numbers seem to make sense.  When you analyze them on the real production environment - they only mislead (as does the sysmon bit in the Indicator column related to them).  

Any insights?

Thanks,

Andrew

ps.  PERFORMANCE SCALABILITY ENHANCEMENTS IN SAP ADAPTIVE SERVER® ENTERPRISE has a neat section on PC sizing which, too, rely on monProcedureCacheModuleUsage.  However, the values are taken as simple aggregates - without any respect to their cumulative nature.  Was ASE bounced to take correct measurement?  How reliable are the HWM/Reuse numbers in that paper?

Good day,

According to ASE Certifications on Linux (RedHat) - SAP ASE - SCN Wiki, ASE 15.7 SP122 is certified on  RHEL 7.

Does this certification include Red Hat 7 update1 and  higher?

PS : Is this URL the new site for checking certifications( as the old http://certifications.sybase.com is gone )?

Thanks..

Regards

Jose-Miguel

Anyone knows where the documentation for ASE 16 Sp02 may be found?

Thanks.

When updating a model from the db the window listing them doesn't have them sorted. I've only seen this problem with ASE. How do I get them sorted?

I just noticed in the system table poster for ASE 15.7 there's a new system table called: syspasswordhistory

For ASE 16.0 the table is not there anymore, and it's not documented in the security guide.

Are there any plans to implement password history functionality?

Would be useful to know because of custom implementations with sp_extrapwdchecks and future migrations

Bonjour,

   I need to change the backupserver file without shutting down the backupserver.  I know how to change the serverlog file using sp_errorlog but can't find a way to do the same with the backupserver.  Is there a way to connect to the backup server and issue the same command?  I need help on this.

Thanks for your time and expertise.

Best Regards,

William

(Using ASE 15.7 SP110+) I have been exploring the use of global login triggers for a variety of purposes.   I read that I had to be careful about inadvertently locking out "sa" and other necessary system-roled users.    I could use specific, individual login triggers as well/instead, but would like the global option as a means of generically catching all login attempts to potentially write to my own, custom audit log.

I note that (non global) login trigger stored procedures "cannot be dropped" until/unless disassociated from login triggers.    I tried an experiment with my global login trigger - wherein I removed the supporting stored procedure (without previously disassociating it from the global login trigger).   Such immediately blocked all logins (including sa).   Is that the intended behavior?  Or is it an oversight - such that dropping the stored procedure supporting a global login trigger should not be allowed until disassociation from the global login trigger has occurred?

I look forward to reading your responses.

Thanks,

Ben Black

Right now I have two instances of ASE running in the same server.  I have ASE COCKPIT running in that machine but when I open the COCKPIT, it only shows one system.

How can i add the other system to the cockpit?

> showserver

F S UID        PID  PPID  C PRI  NI ADDR SZ WCHAN  STIME TTY          TIME CMD

0 S sybase   19828 19827  5  80   0 - 776226 futex_ 11:15 ?       00:01:14 /opt/sap/ASE-16_0/bin/dataserver -d/opt/sap/data2k/master.dat -e/opt/sap/ASE-16_0/install/TESTENVASE16_2k.log -c/opt/sap/ASE-16_0/TESTENVASE16_2k.cfg -M/opt/sap/ASE-16_0 -N/opt/sap/ASE-16_0/sysam/TESTENVASE16_2k.properties -i/opt/sap -sTESTENVASE16_2k

0 S sybase   12181 12180  1  80   0 - 743970 futex_ Feb11 ?       01:53:33 /opt/sap/ASE-16_0/bin/dataserver -d/opt/sap/data/master.dat -e/opt/sap/ASE-16_0/install/TESTENVASE16.log -c/opt/sap/ASE-16_0/TESTENVASE16.cfg -M/opt/sap/ASE-16_0 -N/opt/sap/ASE-16_0/sysam/TESTENVASE16.properties -i/opt/sap -sTESTENVASE16 -T7862