any issues to restore dump file of ASE 12.0 (32bit) to a ASE 12.0 (64bit) system ?
Does anyone know whether there is an issue that we restore
the dump file (not master and system db) of ASE 12.0 (32bit)
to a ASE 12.0 (64bit) system ? Assume that both system DBs
are the same.
> Does anyone know whether there is an issue that we restore
> the dump file (not master and system db) of ASE 12.0
> (32bit) to a ASE 12.0 (64bit) system ? Assume that both
> system DBs are the same.
If you have a recent ebf of ASE 12.0 (say 184.108.40.206 or later)
than no problem. Earlier ebfs had a few problems....ASE 220.127.116.11 / SWR 8775 UPGRADE TO ASE 18.104.22.168/EBF 10628 PERFORMANCE PROBLEM
We recently upgraded ASE 22.214.171.124/SWR 8775 to ASE 126.96.36.199/EBF 10628.
Some queries stopped returning resultsets. Recompiled the stored procs which
fixed the issue.
But the queries are running slower now. The overall performance of the app
has become sluggish.
The CPU is generally running higher as well!
Have also set LD_LIBRARY_PATH_64 to include the new Solaris 8 threads
Anybody any insights into this? How can we get back to the pre-upgrade
performance levels short of rolling back the EBF.
I guess 188.8.131.52 requires some Solaris ...ASE 184.108.40.206 to ASE 12.5 and Rep Server 12.1
We are planning the upgrade of our ASE 220.127.116.11 64bit on AIX
4.3.3 to ASE 12.5 64bit on AIX 4.3.3. We are also using Rep
Server 12.1 with these two servers. My question is do I
need to upgrade Rep Server as well, or will 12.1 Rep Server
Work with ASE 12.5.
Also, we will be upgrading AIX to 5.1 as well.
Any advice is appreciated.
It will work, however you wont be able to use any of the 12.5 new datatypes,
and the rep_agents will spit out annoying error/warning messages everytime
they are restarted. Our production system has been running that way for
about ye...Can't construct query plan in ASE 12.0
Error 325 is being returned when trying to execute a stored procedure on
Adaptive Server Enterprise/12.0/P/SWR 8773 ESD 1/RS6000/AIX
4.3.2/1580/64bit/FBO/Tue Dec 7 03:29:32 1999 ...
this is the code causing the error when running on version listed above...
it's a sub-query within a stored proc
AND SBSB.HIST_ROW_ID = (select
SBSB2.SBSB_CK = SBSB.SBSB_CK
AND CONVERT(CHAR(10),SBEL.SBEL_INSQ_DT,101) = CONVERT(CHAR
When executing same stored procedure on AS...Migrating from ASE 12.0 32-bit to ASE 12.0 64-bit
Has anyone run into any problems migrating from 32-bit to 64-bit?
...Migrating from ASE 12.0 32-bit to ASE 12.0 64-bit
Has anyone run into any problems migrating from 32-bit to 64-bit?
...ASE 12.0 and ASE 12.5 optional features
Can anyone knows what are the optional features of ASE 12.0 and ASE 12.5??
ASE 12.0 :
* DTM (distribute transaction management)
* HA (High availability)
* JAVA (Java support in the database)
* Security services.
* EJB support in the database.
* XFS (extended file system support)
* Directory services
* Extended full text search
* Java option now includes xml support in ASE.
<firstname.lastname@example.org> wrote in message
...Upgrading from ASE 12.0 to ASE 12.5.2
I am basically thinking of upgrading ASE 12.0.x to ASE 12.5.2.
How would the migration process be. Is it straight dump and load or
> Hi everyone,
> I am basically thinking of upgrading ASE 12.0.x to ASE 12.5.2.
> How would the migration process be. Is it straight dump and load or
> otherwise ??
see the upgrade/installation guide
Senior Consultant Sybase Professional Services
New address per 21 November 2005:
Zo...Upgrade ASE 18.104.22.168 to 22.214.171.124
I upgraded my ASE to version 126.96.36.199. Now one of the application get
a permanent error: "Not enough procedure cache". I increased the proc
cache to 40% (total memory: 1 GB) - no success. When I rolled back to
188.8.131.52 everything works fine (with less procedure cache).
The ASE is running on Solaris 7. The application connects thru the
Merant ODBC driver. I gave the application already back to development
Any help how this can be avoided by a change on the host/server is
I always recommend dropping/recreating all of the stored...ASE 12.5.2 to ASE 184.108.40.206
I have to return to ASE 220.127.116.11 from ASE 12.5.2.
I created a new server and did a dump/load of a user database and
that seems to be fine.
Is this a safe way to downgrade ?
Is it necessary to create a new server (master database) or should it
also be possible to shutdown the 12.5.2 server and start it again with
the 18.104.22.168 binary ?
...Performance Degradation after ASE 12.0 upgrade to ASE 12.5
There was a issue posted on 08/06/2002 by 'Bob' related to performance
degradation after upgrade of ASE 11.9.2 to ASE 12.5. I would like to know
whether anyone has found any solution/workaround
to resolve those issues without making any changes in the application code.
We are also facing the same problems here after upgrade of ASE 12.0 to ASE
12.5. The program which takes 10 mins. on ASE 12.0 is taking more than 3
hrs to finish on ASE 12.5 despite of using the same indexes and the program
which takes 3 hrs on ASE 12.0 is taking more than 24 hours on ASE 12.5. ...Upgrading from ASE (32-bit) 22.214.171.124 on Solaris 2.8 64-bit to ASE(64-bit) 12.5.1 on Solaris 64-bit
We are planning to upgrade our ASE servers from a 32-bit ASE 126.96.36.199 to
64-bit ASE 12.5.1 on Solaris 8. Could you please give what are the steps to
be taken care and how do I start with ( Do I have to first upgrade to
32-bit12.5.1 and then upgrade to 64-bit ASE 12.5.1, or directly upgrade from
32-bit 188.8.131.52 to 64-bit 12.5.1 ?).
Could you also please point to some documentation (about upgrading 32-bit
184.108.40.206 to 64-bit 12.5.1).
...Upgrade from ASE 220.127.116.11 to ASE 12.5.1
This is a multi-part message in MIME format.
Content-Type: text/plain; charset="iso-8859-1"
I've just upgraded from ASE 18.104.22.168 to ASE 12.5.1. I tried
to start the server, but it won't startup.
Here is the message:
sybase(ASE1250)328 /app/sybase/ASE-12_5/install -->
startserver -f RUN_AMXDB
sybase(ASE1250)329 /app/sybase/ASE-12_5/install -->
00:00000:00000:2004/01/05 21:37:44.10 kernel Use license
00:00000:00000:2004/01/05 21:37:44.10 ker...Migration from ASE 12.0 ( HPUX ) to ASE 12.5 ( Solaris 8 )
I'd like to migrate an ASE 22.214.171.124 (roman8) on HPUX 11 with many DBs
to an ASE 126.96.36.199 (*roman8*) on Solaris 8. I know it's not the default charset on solaris.
I've made dump on HPUX, copy it on Sun box and load it. I know it's not supported by Sybase ( cross plateform dump ).
However, it seems to be OK, the upgrade works well, the dbcc (check table, alloc) did not reveal error. I think it's not
supported only because the charset deffers ( by default ) on the plateform.
What do you think of this ? is there others checks to do ?
What kind of corruption or...