Failing ASE creation.

I have installed ASE 12.5 and am trying to build the master device. 
I believe the following excerpt is the cause, but have no idea how to fix 
it.  Can anyone shed some light on this?

00:00000:00001:2001/12/20 13:46:24.68 kernel  ueshutdown: exiting
ld.so.1: /opt/sybase/ASE-12_5/bin/dataserver: fatal: relocation error: file 

/opt/sybase/ASE-12_5/bin/dataserver: symbol 
__1cG__CrunVdo_exit_code_in_range6Fpv1_v_: referenced symbol not found


The complete output below...

Building Adaptive Server 'hades':

Writing entry into directory services... Directory services entry complete.
Building master device... Task failed
00:00000:00001:2001/12/20 13:45:19.82 server  Database 'master': beginning 
upgrade step [ID     2]: Bootstrap basic system catalogs in database. 
00:00000:00001:2001/12/20 13:45:20.44 server  Database 'master': beginning 
upgrade step [ID     3]: creating index (table systypes, index ncsystypes)
00:00000:00001:2001/12/20 13:45:20.60 server  Database 'master': beginning 
upgrade step [ID     4]: creating index (table sysobjects, index 
ncsysobjects)
00:00000:00001:2001/12/20 13:45:20.75 server  Database 'master': beginning 
upgrade step [ID    20]: creating table (table sysusages)
00:00000:00001:2001/12/20 13:45:21.08 server  Database 'master': beginning 
upgrade step [ID    21]: creating table (table sysdatabases)
00:00000:00001:2001/12/20 13:45:21.44 server  Database 'master': beginning 
upgrade step [ID    22]: creating table (table sysdevices)
00:00000:00001:2001/12/20 13:45:21.74 server  Database 'master': beginning 
upgrade step [ID    23]: creating table (table sysmessages)
00:00000:00001:2001/12/20 13:45:22.04 server  Database 'master': beginning 
upgrade step [ID    24]: creating table (table sysconfigures)
00:00000:00001:2001/12/20 13:45:22.42 server  Database 'master': beginning 
upgrade step [ID    25]: creating table (table syscharsets)
00:00000:00001:2001/12/20 13:45:22.75 server  Database 'master': beginning 
upgrade step [ID    26]: creating table (table sysprocedures)
00:00000:00001:2001/12/20 13:45:23.04 server  Database 'master': beginning 
upgrade step [ID    27]: creating table (table syscomments)
00:00000:00001:2001/12/20 13:45:23.33 server  Database 'master': beginning 
upgrade step [ID    28]: creating table (table syssegments)
00:00000:00001:2001/12/20 13:45:23.49 server  Database 'master': beginning 
upgrade step [ID    29]: creating table (table sysprotects)
00:00000:00001:2001/12/20 13:45:23.79 server  Database 'master': beginning 
upgrade step [ID    30]: creating table (table sysusers)
00:00000:00001:2001/12/20 13:45:24.19 server  Database 'master': beginning 
upgrade step [ID    31]: creating table (table sysalternates)
00:00000:00001:2001/12/20 13:45:24.45 server  Database 'master': beginning 
upgrade step [ID    32]: creating table (table sysdepends)
00:00000:00001:2001/12/20 13:45:24.71 server  Database 'master': beginning 
upgrade step [ID    33]: creating table (table syskeys)
00:00000:00001:2001/12/20 13:45:25.03 server  Database 'master': beginning 
upgrade step [ID    35]: creating table (table sysprocesses)
00:00000:00001:2001/12/20 13:45:25.22 server  Database 'master': beginning 
upgrade step [ID    36]: creating table (table syslogins)
00:00000:00001:2001/12/20 13:45:25.64 server  Database 'master': beginning 
upgrade step [ID    37]: creating table (table syslocks)
00:00000:00001:2001/12/20 13:45:25.82 server  Database 'master': beginning 
upgrade step [ID    38]: creating table (table syscurconfigs)
00:00000:00001:2001/12/20 13:45:25.94 server  Database 'master': beginning 
upgrade step [ID    39]: creating table (table sysservers)
00:00000:00001:2001/12/20 13:45:26.26 server  Database 'master': beginning 
upgrade step [ID    40]: creating table (table sysremotelogins)
00:00000:00001:2001/12/20 13:45:26.54 server  Database 'master': beginning 
upgrade step [ID    41]: creating table (table sysmonitors)
00:00000:00001:2001/12/20 13:45:26.69 server  Database 'master': beginning 
upgrade step [ID    42]: creating table (table sysengines)
00:00000:00001:2001/12/20 13:45:26.80 server  Database 'master': beginning 
upgrade step [ID    43]: creating table (table syslanguages)
00:00000:00001:2001/12/20 13:45:27.20 server  Database 'master': beginning 
upgrade step [ID    44]: creating table (table systestlog)
00:00000:00001:2001/12/20 13:45:27.25 server  Database 'master': beginning 
upgrade step [ID    45]: creating table (table syssrvroles)
00:00000:00001:2001/12/20 13:45:27.55 server  Database 'master': beginning 
upgrade step [ID    46]: creating table (table sysloginroles)
00:00000:00001:2001/12/20 13:45:27.91 server  Database 'master': beginning 
upgrade step [ID    80]: creating table (table sysattributes)
00:00000:00001:2001/12/20 13:45:28.37 server  Database 'master': beginning 
upgrade step [ID    81]: Load initial set of attribute-definition rows into 

SYSATTRIBUTES. 
00:00000:00001:2001/12/20 13:45:40.90 server  Warning: Using only the first 
30 
characters for password
00:00000:00001:2001/12/20 13:45:50.58 server  Database 'master': beginning 
upgrade step [ID   251]: creating table (table syslogshold)
00:00000:00001:2001/12/20 13:45:50.82 server  Database 'master': beginning 
upgrade step [ID   252]: creating table (table syslisteners)
00:00000:00001:2001/12/20 13:45:51.06 server  Database 'master': beginning 
upgrade step [ID   253]: creating table (table syssecmechs)
00:00000:00001:2001/12/20 13:45:51.29 server  Database 'master': beginning 
upgrade step [ID   600]: creating table (table sysreferences)
00:00000:00001:2001/12/20 13:45:51.84 server  Database 'master': beginning 
upgrade step [ID   601]: creating table (table sysconstraints)
00:00000:00001:2001/12/20 13:45:52.26 server  Database 'master': beginning 
upgrade step [ID   602]: creating table (table sysusermessages)
00:00000:00001:2001/12/20 13:45:52.62 server  Database 'master': beginning 
upgrade step [ID   603]: creating table (table systhresholds)
00:00000:00001:2001/12/20 13:45:52.93 server  Database 'master': beginning 
upgrade step [ID   604]: creating table (table sysroles)
00:00000:00001:2001/12/20 13:45:53.23 server  Database 'master': beginning 
upgrade step [ID   605]: executing SQL statement (declare @rid smallint 
delete 
sysro)
00:00000:00001:2001/12/20 13:45:53.60 server  Database 'master': beginning 
upgrade step [ID   606]: executing SQL statement (select 
lct_admin('lastchance', 
db_i)
00:00000:00001:2001/12/20 13:45:53.74 server  Database 'master': beginning 
upgrade step [ID  1013]: creating table (table syspartitions)
00:00000:00001:2001/12/20 13:45:54.08 server  Database 'master': beginning 
upgrade step [ID  1025]: creating table (table systimeranges)
00:00000:00001:2001/12/20 13:45:54.42 server  Database 'master': beginning 
upgrade step [ID  1026]: executing SQL statement (if not exists (select 1 
from 
systim)
00:00000:00001:2001/12/20 13:45:54.48 server  Database 'master': beginning 
upgrade step [ID  1027]: creating table (table sysresourcelimits)
00:00000:00001:2001/12/20 13:45:54.81 server  Database 'master': beginning 
upgrade step [ID  1082]: executing SQL statement (if not exists (select 1 
from 
sysatt)
00:00000:00001:2001/12/20 13:45:55.00 server  Database 'master': beginning 
upgrade step [ID  1124]: creating table (table systabstats)
00:00000:00001:2001/12/20 13:45:55.38 server  Database 'master': beginning 
upgrade step [ID  1125]: creating table (table sysstatistics)
00:00000:00001:2001/12/20 13:45:56.00 server  Database 'master': beginning 
upgrade step [ID  1126]: Initialize systabstats with valid statistics 
00:00000:00001:2001/12/20 13:45:57.28 server  Database 'master': beginning 
upgrade step [ID  1131]: Creating/Updating the last chance threshold for 
logsegment. 
00:00000:00001:2001/12/20 13:45:57.31 server  Database 'master': beginning 
upgrade step [ID  1201]: creating table (table sysxtypes)
00:00000:00001:2001/12/20 13:45:57.75 server  Database 'master': beginning 
upgrade step [ID  1205]: creating table (table sysjars)
00:00000:00001:2001/12/20 13:45:58.23 server  Database 'master': beginning 
upgrade step [ID  1206]: executing SQL statement (if not exists (select 1 
from 
systyp)
00:00000:00001:2001/12/20 13:45:58.28 server  Database 'master': beginning 
upgrade step [ID  1212]: creating table (table systransactions)
00:00000:00001:2001/12/20 13:45:58.53 server  Database 'master': beginning 
upgrade step [ID  1213]: executing SQL statement (update sysobjects set 
sysstat2 
= sy)
00:00000:00001:2001/12/20 13:45:58.68 server  Database 'master': beginning 
upgrade step [ID  1214]: executing SQL statement (if not exists (select 1 
from 
syssrv)
00:00000:00001:2001/12/20 13:45:58.71 server  Database 'master': beginning 
upgrade step [ID  1226]: executing SQL statement (insert sysattributes 
(class, 
attrib)
00:00000:00001:2001/12/20 13:45:58.90 server  Database 'master': beginning 
upgrade step [ID  1240]: creating table (table sysqueryplans)
00:00000:00001:2001/12/20 13:45:59.43 server  Database 'master': beginning 
upgrade step [ID  1241]: executing SQL statement (insert into sysattributes 
 
(class, )
00:00000:00001:2001/12/20 13:45:59.63 server  Database 'master': beginning 
upgrade step [ID  1242]: creating table (table syssessions)
00:00000:00001:2001/12/20 13:45:59.85 server  Database 'master': beginning 
upgrade step [ID  1245]: executing SQL statement (if not exists (select 1 
from 
syssrv)
00:00000:00001:2001/12/20 13:46:00.01 server  Database 'master': beginning 
upgrade step [ID  1249]: executing SQL statement (if (select 
suser_id('sa')) is 
not n)
00:00000:00001:2001/12/20 13:46:00.15 server  Database 'master': beginning 
upgrade step [ID  1337]: executing SQL statement (if not exists (select 1 
from 
sysser)
00:00000:00001:2001/12/20 13:46:00.32 server  Database 'master': beginning 
upgrade step [ID  1338]: executing SQL statement (delete from sysconfigures 

where con)
00:00000:00001:2001/12/20 13:46:00.36 server  Database 'master': beginning 
upgrade step [ID  1339]: creating table (table syscertificates)
00:00000:00001:2001/12/20 13:46:00.73 server  Database 'master': beginning 
upgrade step [ID  1340]: executing SQL statement (update systypes set 
length=@@maxpag)
00:00000:00001:2001/12/20 13:46:00.77 server  Database 'master': beginning 
upgrade step [ID  1344]: executing SQL statement (update sysattributes set 
int_value=)
00:00000:00001:2001/12/20 13:46:00.92 server  Database 'master': beginning 
upgrade step [ID  1345]: executing SQL statement (update sysattributes set 
int_value=)
00:00000:00001:2001/12/20 13:46:01.10 server  Database 'master': beginning 
upgrade step [ID  1400]: noting the present database upgrade level 
00:00000:00001:2001/12/20 13:46:01.17 server  Database 'model' appears to 
be at 
an older revision than the present installation; SQL Server will assess it, 
and 
upgrade it as required.
00:00000:00001:2001/12/20 13:46:01.19 server  Database 'model': beginning 
upgrade step [ID     1]: Initialize disk and create empty allocation units 
on 
master device. 
00:00000:00001:2001/12/20 13:46:02.60 server  Database 'model': beginning 
upgrade step [ID     2]: Bootstrap basic system catalogs in database. 
00:00000:00001:2001/12/20 13:46:03.15 server  Database 'model': beginning 
upgrade step [ID     3]: creating index (table systypes, index ncsystypes)
00:00000:00001:2001/12/20 13:46:03.29 server  Database 'model': beginning 
upgrade step [ID     4]: creating index (table sysobjects, index 
ncsysobjects)
00:00000:00001:2001/12/20 13:46:03.46 server  Database 'model': beginning 
upgrade step [ID    26]: creating table (table sysprocedures)
00:00000:00001:2001/12/20 13:46:03.72 server  Database 'model': beginning 
upgrade step [ID    27]: creating table (table syscomments)
00:00000:00001:2001/12/20 13:46:03.98 server  Database 'model': beginning 
upgrade step [ID    28]: creating table (table syssegments)
00:00000:00001:2001/12/20 13:46:04.09 server  Database 'model': beginning 
upgrade step [ID    29]: creating table (table sysprotects)
00:00000:00001:2001/12/20 13:46:04.41 server  Database 'model': beginning 
upgrade step [ID    30]: creating table (table sysusers)
00:00000:00001:2001/12/20 13:46:04.76 server  Database 'model': beginning 
upgrade step [ID    31]: creating table (table sysalternates)
00:00000:00001:2001/12/20 13:46:05.02 server  Database 'model': beginning 
upgrade step [ID    32]: creating table (table sysdepends)
00:00000:00001:2001/12/20 13:46:05.29 server  Database 'model': beginning 
upgrade step [ID    33]: creating table (table syskeys)
00:00000:00001:2001/12/20 13:46:05.66 server  Database 'model': beginning 
upgrade step [ID    80]: creating table (table sysattributes)
00:00000:00001:2001/12/20 13:46:06.21 server  Database 'model': beginning 
upgrade step [ID   600]: creating table (table sysreferences)
00:00000:00001:2001/12/20 13:46:06.82 server  Database 'model': beginning 
upgrade step [ID   601]: creating table (table sysconstraints)
00:00000:00001:2001/12/20 13:46:07.26 server  Database 'model': beginning 
upgrade step [ID   602]: creating table (table sysusermessages)
00:00000:00001:2001/12/20 13:46:07.61 server  Database 'model': beginning 
upgrade step [ID   603]: creating table (table systhresholds)
00:00000:00001:2001/12/20 13:46:07.92 server  Database 'model': beginning 
upgrade step [ID   604]: creating table (table sysroles)
00:00000:00001:2001/12/20 13:46:08.26 server  Database 'model': beginning 
upgrade step [ID   605]: executing SQL statement (declare @rid smallint 
delete 
sysro)
00:00000:00001:2001/12/20 13:46:08.61 server  Database 'model': beginning 
upgrade step [ID   606]: executing SQL statement (select 
lct_admin('lastchance', 
db_i)
00:00000:00001:2001/12/20 13:46:08.76 server  Database 'model': beginning 
upgrade step [ID  1013]: creating table (table syspartitions)
00:00000:00001:2001/12/20 13:46:09.07 server  Database 'model': beginning 
upgrade step [ID  1124]: creating table (table systabstats)
00:00000:00001:2001/12/20 13:46:09.42 server  Database 'model': beginning 
upgrade step [ID  1125]: creating table (table sysstatistics)
00:00000:00001:2001/12/20 13:46:09.91 server  Database 'model': beginning 
upgrade step [ID  1126]: Initialize systabstats with valid statistics 
00:00000:00001:2001/12/20 13:46:10.62 server  Database 'model': beginning 
upgrade step [ID  1131]: Creating/Updating the last chance threshold for 
logsegment. 
00:00000:00001:2001/12/20 13:46:10.75 server  Database 'model': beginning 
upgrade step [ID  1201]: creating table (table sysxtypes)
00:00000:00001:2001/12/20 13:46:11.22 server  Database 'model': beginning 
upgrade step [ID  1205]: creating table (table sysjars)
00:00000:00001:2001/12/20 13:46:11.66 server  Database 'model': beginning 
upgrade step [ID  1206]: executing SQL statement (if not exists (select 1 
from 
systyp)
00:00000:00001:2001/12/20 13:46:11.82 server  Database 'model': beginning 
upgrade step [ID  1240]: creating table (table sysqueryplans)
00:00000:00001:2001/12/20 13:46:12.29 server  Database 'model': beginning 
upgrade step [ID  1241]: executing SQL statement (insert into sysattributes 
 
(class, )
00:00000:00001:2001/12/20 13:46:12.46 server  Database 'model': beginning 
upgrade step [ID  1340]: executing SQL statement (update systypes set 
length=@@maxpag)
00:00000:00001:2001/12/20 13:46:12.61 server  Database 'model': beginning 
upgrade step [ID  1400]: noting the present database upgrade level 
00:00000:00001:2001/12/20 13:46:12.71 server  CREATE DATABASE: allocating 
1024 
logical pages (2.0 megabytes) on disk 'master'.
00:00000:00001:2001/12/20 13:46:23.46 server  Database sybsystemdb 
successfully 
created.
00:00000:00001:2001/12/20 13:46:23.74 server  Recovering database 
'sybsystemdb'.
00:00000:00001:2001/12/20 13:46:23.76 server  Redo pass of recovery has 
processed 2 committed and 0 aborted transactions.
00:00000:00001:2001/12/20 13:46:24.04 server  Boot Count: 1
00:00000:00001:2001/12/20 13:46:24.11 server  Checking external objects.
00:00000:00001:2001/12/20 13:46:24.21 server  Database 'sybsystemdb' is now 

online.
00:00000:00001:2001/12/20 13:46:24.24 server  Now loading SQL Server's new 
default sort order and character set
00:00000:00001:2001/12/20 13:46:24.24 server  Checking sysobjects: Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.24 server  Checking systypes: Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.25 server  Checking sysusers: Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.25 server  Checking sysreferences: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.25 server  Checking sysreferences: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.25 server  Checking sysreferences: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.26 server  Checking sysattributes: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.26 server  Checking sysattributes: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.27 server  Checking sysxtypes: Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.30 server  Checking sysjars: Logical 
pagesize 
is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.30 server  Checking sysobjects: Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.31 server  Checking systypes: Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.34 server  Checking sysusers: Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.36 server  Checking sysreferences: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.38 server  Checking sysreferences: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.38 server  Checking sysreferences: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.39 server  Checking sysattributes: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.43 server  Checking sysattributes: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.44 server  Checking sysxtypes: Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.46 server  Checking sysjars: Logical 
pagesize 
is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.49 server  Checking sysobjects: Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.49 server  Checking systypes: Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.50 server  Checking sysusers: Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.50 server  Checking sysreferences: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.50 server  Checking sysreferences: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.50 server  Checking sysreferences: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.51 server  Checking sysattributes: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.53 server  Checking sysattributes: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.56 server  Checking sysxtypes: Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.56 server  Checking sysjars: Logical 
pagesize 
is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.57 server  Checking sysdatabases: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.57 server  Checking syslogins: Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.57 server  Checking sysdevices: Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.57 server  Checking sysconfigures: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.58 server  Checking sysservers: Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.59 server  Checking sysremotelogins: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.59 server  Checking syslanguages: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.59 server  Checking syslanguages: 
Logical 
pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.59 server  Checking syscharsets: Logical 

pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.60 server  Checking sysresourcelimits: 
Logical pagesize is 2048 bytes
00:00000:00001:2001/12/20 13:46:24.68 server  Default Sort Order 
successfully 
changed.
00:00000:00001:2001/12/20 13:46:24.68 server  SQL Server shutdown after 
verifying System Indexes.
00:00000:00001:2001/12/20 13:46:24.68 kernel  ueshutdown: exiting
ld.so.1: /opt/sybase/ASE-12_5/bin/dataserver: fatal: relocation error: file 

/opt/sybase/ASE-12_5/bin/dataserver: symbol 
__1cG__CrunVdo_exit_code_in_range6Fpv1_v_: referenced symbol not found
Writing RUN_hades file...
RUN_hades file complete.
Starting server... Task failed
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.  Open Client message: 'ct_connect(): directory service layer: internal 
directory control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Open Client message: 'ct_connect(): directory service layer: internal 
directory 
control layer error: Requested server name not found.
'.
Unable to boot server 'hades'.

Server 'hades' was not created.

Done


Thank you in advance.
0
Brian_Gillock
12/20/2001 6:37:22 PM
sybase.ase.administration 7058 articles. 2 followers. Follow

1 Replies
713 Views

Similar Articles

[PageSpeed] 49
Get it on Google Play
Get it on Apple App Store

Brian_Gillock wrote...
> I have installed ASE 12.5 and am trying to build the master device. 
> I believe the following excerpt is the cause, but have no idea how to fix 
> it.  Can anyone shed some light on this?
> 
> 00:00000:00001:2001/12/20 13:46:24.68 kernel  ueshutdown: exiting
> ld.so.1: /opt/sybase/ASE-12_5/bin/dataserver: fatal: relocation error: file 
> 
> /opt/sybase/ASE-12_5/bin/dataserver: symbol 
> __1cG__CrunVdo_exit_code_in_range6Fpv1_v_: referenced symbol not found

You didn't specify the platform and version of the O/S you were installing on.  I'm 
guessing that you are installing on Solaris, probably 64 bit.  You MUST be on 2.8 and have 
all the current O/S patches installed.  Take care of that and these errors should go away.
-- 
Jim Egan [TeamSybase]
Senior Consultant
Sybase Professional Services
0
Jim
12/21/2001 1:56:27 AM
Reply:

Similar Artilces:

ASE and ASE
Could it be possible to take scripts from ASA and load them in an ASE Any information is welcome jean-fran�ois ASA supports a fairly large sub-set of Transact-SQL, so if you write your stored procedures and triggers in ASA using T-SQL, you should be able to create scripts that will run against both ASE and ASA. If you're planning to do this though, I would suggest developing your database schema against ASA, since everything you write in T-SQL in ASA will be supported on ASE, but the reverse is not true. Check out the section in the ASA documentation entitled "Tra...

ASE to ASE
Hi, Is anyone out there doing ASE to ASE replication using SQL remote? If you are have created your own version of the SSEXTRACT utility to set up a replicant database in ASE rather than ASA? Or does anyone know if SYBASE has created a version SSEXTRACT for use with ASE to ASE replication? Thanks in advance Doug Trainer Hi Douglas, I thought the SQL Remote Replication support in ASE11.5 was meant for a consolidate-database only (by design)! At least that was what Sybase said when they announced support for SQL Remote technology support in ASE11.5. I will be happy to...

ASA To ASE - VS
What are the differents in terms of configuring SQL Remote Between ASA to ASE and ASE To ASE ? You should start with the Help file and then ask specific questions: Data Replication with SQL Remote PART 5. Appendix APPENDIX A. Enterprise and Anywhere: Differences There are many differences, so begin there. -- David Fishburn Sybase Please only post to the newsgroup BH Ong <bhong@tm.net.my> wrote in message news:01bf4b98$33183580$7ccdc8c8@virtual-branch... > What are the differents in terms of configuring SQL Remote Between ASA to > ASE and ASE To ASE ...

Adding ASE to existing ASE-to-ASE Installation
I am using all ASE's in my SQLRemote setup. My current installation consists of a Consolidated ASE & 2 Remote ASE's. My attempt to add another Remote ASE to the existing installation consists of these steps: - Install the sqlremote system objects in the new Remote - Install the stable queues in the new Remote - Manually extract a bcp file of the shared table from the Cons server - Configure the Cons server for another subscriber - Configure the new Remote's shared table, publications, & subscriptions. - Manually b...

Loading ASE 15 beta2 --> ASE 15 fails
Having issues loading a dump from ASE 15 beta2 into ASE 15. Beta license expired so installed new copy of ASE 15 and the dumps from beta2 do not load. Have tried doing remote load into ASE 15 using beta2 backup server. Issues here because dumps done with level 4 compression: 1> load database dbadmin from "compress::4::/usr/sybase/dump/IT_TEST.dbadmin_onite_0.dat" at IT_BETA_back 2> go Backup Server: 5.21.2.1: Remote DUMP/LOAD is not allowed when interfacing to a stripe for device 'compress::4::/usr/sybase/dump/IT_TEST.dbadmin_onite_0.dat'. .... 30 10:5...

Dump/Load (from ASE 12.5.4 to ASE 15.x) - VS.
Hi All, We are in the process of planning the upgrade of our ASE 12.5.4 dataservers to ASE 15.x. What is the most recommended way to upgrade ASE dataservers from ASE 12.5.4 to ASE 15.x? Potential options: 1) Install new instances of ASE 15.x and load database dumps from our ASE 12.5.4 dataservers to the newly installed ASE 15.x dataservers. - OR - 2) Use the ASE upgrade utility (sqlupgrade) to upgrade our existing ASE 12.5.4 dataservers to ASE 15.x. What are the Pros vs. Cons for loading a 12.5.4 database into a 15.x ASE dataserver versus performing an ASE dataserv...

Fail to online database(ASE 12.5->ASE 15.0 developer)
Hi Everyone, Could you please help me to take a look at the error? It happened when I want to online databse, I can load database successfully:-), but failed to online...... I backup up the database from ASE 12.5, and restore it to ASE 15.0 developer... 1> online database AdventureWorksDW 2> go Started estimating recovery log boundaries for database 'AdventureWorksDW'. Database 'AdventureWorksDW', checkpoint=(15436, 11), first=(15436, 11), last=(15436, 11). Completed estimating recovery log boundaries for database 'AdventureWorksDW'. Started ANA...

Why does the following query fail on ASE 15.0.2 but work on ASE 12.5.4?
Connection conn = getConnection(); PreparedStatement stmt = conn.prepareStatement("select 'test' from syscolumns where ? = ?"); stmt.setString(1, "test"); stmt.setString(2, "test"); stmt.execute(); The error is "Implicit conversion from datatype 'VARCHAR' to 'INT' is not allowed. Use the CONVERT function to run this query." I think I found the solution, which is that the database needs to know what type to expect for the parameter marker. Therefore using an explicit conversion (as mentioned in the error me...

Solaris ASE to Linux ASE
We are looking into using Replication Server to Set up Warm Standby of Production ASE databases - Primary site being on Solaris platform - Standby Copy on Linux. Does any utilize this configuration ? What is the best way to initialize data on the Standby Server ? What other issues should I be concerned with ? Hi, Technically you can setup Warm Standby across platforms. It may work well too with Replication Server. However, you cannot dump and load the databases (cross platform dump and load not supported), hence there will be issues when you need to resync your databases. Eac...

sql-remote between ASE and ASE
hello! sql-remote document don't give us help with replication with ASE and ASE. i need detail how to do it. i use ASE12 + NT4.0 + SQL Remote6.0.2 . i test it in the list 1�� define messagetype : smtp 2�� define use_name :one is publisher,the other is remote user_name 3�� define publisher,publication,subscription 4��execute ssremote.exe to receive or send message I failed at the step of extract database .i don't extract the database . please help me ,tell me the datail of sql-remote confige. Thanks a lot , ...

SQL Remote ASE
hi did anybody know when SQL Remote support blob (image, text) replicacion for ASE - ASE? our company need this feature. joan caceres electro sur este s.a.a. Hello Joan, Support for image and text replication with SQL Remote went in as of ASA 6 mainline, 6.0.01.1256, and SA maintenance 5.5.04 build 1938. Regards, Bob Bauer Sybase Technical Support jmcd wrote: > hi > > did anybody know when SQL Remote support blob (image, text) replicacion for > ASE - ASE? > > our company need this feature. > > joan caceres > electro sur este ...

Replication between ASE and ASE URGENT
HI everybody Can you help me please with the following question. We need to syncronize ASE to ASE ( bidirectional) Initially, it was planned to implement with SQL remote, but it isn't available. With replication server, it isn't a solution beacuse, the customer doesn=B4t have a comunntication channel all time. We think use Mobiliink Server to replictase ASE to ASE, but using an ASA in the middle, so that, first it replicate ASE to ASA, and later, ASA to ASE, is it this feasible ??? Thanks four your answer "Marco" <mbarrion@uniplex.com.ec> wr...

sql remote ase to ase
can I use sql remote ro replicate data form ase to ase or only from asa to ase and asa to asa ? I would also recommend that you read over the following tech doc; Implementing ASE to ASE Server SQL Remote Replication http://my.sybase.com/detail?id=1009730 Ian Bater iAnywhere Solutions Reg Domaratzki wrote: > Just be aware of the limitations pointed out in the documentation when using ASE as a remote database. > > Replication and Synchronization Guide > PART 4. Appendixes > APPENDIX A. Enterprise and Anywhere: Differences > > Limitations ...

ASE workgroup
hi, what the diference between ASE workgroup and ASE Enterprise, to which systems apply workgroup or enterprise. is an AlphaServer 4000 (DIGITAL SERVER 7305) workgroup and unix and ASE 12.0 will be avaliable for true unix (DEC UNIX). thanks in advance ...

Web resources about - Failing ASE creation. - sybase.ase.administration

Institute for Creation Research - Wikipedia, the free encyclopedia
The Institute for Creation Research (ICR) is a Christian apologetics institute in Dallas , Texas that specializes in education, research, and ...

Scientists call for a creation of task force to classify ageing as a disease
Classifying ageing as a disease pushes scientists to call for a creation of a task force to carefully evaluate the basis for the idea.

Hilarious bug report complaining about the creation of Android in 2007
There are many things about Android that makes it my operating system of choice, namely that it gives me choice, and lots of it. Another big ...

Hyundai shows off six custom creations in Vegas
Filed under: Aftermarket , 2015 SEMA Show , Hyundai Hyundai arrives at SEMA with three custom Tuscon crossovers, two Genesis Coupes, and a Veloster ...

"Stoner Jesus Bible Study is the creation of Deb Button, a 40-something mother of two who had never considered ...
"... when Colorado became the first state to legalize recreational marijuana for adults over 21. 'I was majorly conservative,' said Button, who ...

This re-creation of Vienna in 'Minecraft' will blow your mind
Ever been to Vienna? Yeah, us neither. It looks pretty great, but flights are expensive and we're intimidated by its long history of classical ...

Calls for the Creation of the World’s First Official Safe Sex Emojis
DUREX&reg; calls for the creation of the world's first official safe sex emojis in advance of World AIDS Day on December 1. Use #CondomEmoji ...

Florida: 2nd In Job Creation As Unemployment Continues to Fall
CBS Local Florida: 2nd In Job Creation As Unemployment Continues to Fall CBS Local Interior Secretary Ken Salazar (R) greets construction ...

The future of hit TV series creation
Inside the making of successful TV shows with some of the best creators in the business

'Mythbusters' co-host: Creation Museum 'not even wrong'
The topic of Greater Cincinnati’s very own Creation Museum probably didn't come up during the local stop of “MythBusters,” because, as Adam Savage ...

Resources last updated: 12/6/2015 8:34:19 PM