SAP BO SQL Anywhere17 - Profiler errors connecting to SQL central

[dahliahana]

Hello.

SAP BO often stops recently.

For investigation, I would like to check performance, user's memory usage, SQL statements, etc.

I want to get performance data for Anywhere17.

Connecting to the OS, connecting to SQL central, and connecting to Profiler results in an error.

Is there a way to solve this problem?

Please let me know.

[chris_keating]

The profiler minimally requires a v17 database system catalog (achieved by upgrading). This query needs to return at least one row for the Profiler to be able to use the database:

select
    operation, 
    cast( substr( version, 0, locate( version, '.' )  ) as int ) as MajorVersion, 
    version as FuilVersion 
from syshistory 
where 
        operation in ( 'INIT', 'UPGRADE' )
    and MajorVersion = 17

This checks to see if the database was created or upgraded using version 17. If there are no rows returned, the database must either be upgraded or rebuilt with version 17 engine. Both options would result in a database that cannot be run on 16 or older major versions - and depending on the version and build used to perform the rebuild/upgrade, older builds of SQLA 17. Upgrades made changes that only affect the catalog but a rebuild changes the file format and allows for full access of all new features for a given release.

See SQL Anywhere Server Upgrades | SAP Help Portal for additional information on each of the options. More specific docs for each of the options:

• Upgrading a Version 12 or Later Database (SQL Central) | SAP Help Portal
• Rebuilding a Database (SQL Central) | SAP Help Portal

[dahliahana]

Dear.chris.keating

Thank you for your answer.

I checked the SQL statement as your answer, but the answer did not come back.

Will an upgrade be necessary in this case?

※A value was obtained when a new query statement was executed.

Is it different from what you told me?

[chris_keating]

"This query needs to return at least one row for the Profiler to be able to use the database:"

Since there were no rows returned, you will either need to upgrade or rebuild to use the profiler.

I have provided links to each of these options. If you are unsure of how to proceed, please engage a support incident for assistance. If you opt to upgrade, make sure to pay attention to System Privileges Introduced in Upgrades and Distributing Privileges Granted to the UPGRADE ROLE System Privilege After an Upgrade links referenced in the Upgrade documentation .

[dahliahana]

Dear.chris.keating

I'm sorry, but can I ask you more question?

1. SQL Central→ SQL Profiler = I Need "Profiler Upgrade"?

2. I tried running Profiler in a different way.

SQL Control→SQL Profiler

A new error message appears.

Does this problem also need to be upgraded?

[chris_keating]

Unfortunately, I cannot translate the message but I think it is the result of SQL Central running when a SQL Anywhere patch was applied and the java components in %SQLANY17%\java not being updated to match the rest of the SQL Anywhere binaries. Rename that directory i.e., %SQLANY17%\java.bak and rerun the install in Repair mode. This will recreate the directory and its contents. That should resolve the issue.

[dahliahana]

Dear.chris.keating

It's my mistake that I couldn't translate. I'm sorry.

There are currently two folders in the place where BO installed them.

If the 2 folders I found are database and database tools,

Is the error that occurs because the two versions are different?

Is the solution correct to update the database you mentioned?

1.I think it's the database version.

SQLanywhere：17.0.8.4103 SP1

2.Is this the database management tool version?

SQL Anywhere17：17.0.8.4103 SP1

I'm sorry to ask you a lot of questions.

There are many things I don't know because it's my first time managing BO.

I'm gaining strength from your answer. Thank you very, very much.

[chris_keating]

Caveat: I have zero knowledge of BO. I do know that SQL Anywhere is embedded in that product as a database option.

Having 2 versions will cause problems if those versions are not carefully isolated This is likely is the cause of the problem running SQL Central.

Is the E:\SQL Anywhere 17 from a patch provided by BO - the directory structure is not consistent with a SQL Anywhere standalone install?

Do you know which of those SQLA 17 installs is being used?

Can you check the SQLA17 environment variable?

[dahliahana]

Dear.chris.keating

Sorry for the late confirmation.

I don't know why it was divided into two because the BO environment was installed by another team, not me.

The environment variables in SQL17 are as follows.

1. SQL Profiler、SQL Anywhere Ver

In my first question, it said version upgrade, but I checked and I think the version is the same.

I think the version is the same... Which version should I upgrade

[chris_keating]

To use the Profiler, the database *file* needs to be upgraded or rebuilt using SQL Anywhere 17 server/utilities. Please review my initial response from May 29. The database file will need to upgraded or rebuilt using SQL Anywhere 17 binaries.