Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: 8.1.7.4 & svrmgrl - ora-12560

Re: 8.1.7.4 & svrmgrl - ora-12560

From: Sybrand Bakker <gooiditweg_at_sybrandb.demon.nl>
Date: Wed, 07 May 2003 19:30:36 +0200
Message-ID: <bigibvs9calgv7r8l314i8st5pd98lhvvn@4ax.com>


On 7 May 2003 03:25:39 -0700, damianp_at_cgp.co.uk (Damian Powell) wrote:

>Hi,
>
>I recently installed the 8.1.7.4 patch to our Oracle server (running
>on W2K). Since then, I have not been able to create another database.
>One of my colleagues is having a similar problem with another machine
>that has had the same patch. Other systems we have that are 8.1.7.0
>can still successfully run the creation scripts we are using without
>any problems. Can anyone shed any light on this? Your attention is
>appreciated.
>
>I have included a snippet below.
>
>Many thanks,
>Damian.
>
>
>From command prompt:
>
>> D:\oracle\admin\waqd\create\database>e:\oracle\ora81\bin\svrmgrl
>> @d:\oracle\admin\waqd\create\database\waqdrun.sql
>>
>> Oracle Server Manager Release 3.1.7.0.0 - Production
>>
>> Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.
>>
>> ORA-12560: TNS:protocol adapter error
>> Echo ON
>> SVRMGR> connect INTERNAL/oracle
>> ORA-12560: TNS:protocol adapter error
>
>
>waqdrun.sql contains:
>
>spool d:\oracle\admin\waqd\create\logs\createdb
>set echo on
>connect INTERNAL/oracle
>startup nomount pfile="d:\oracle\admin\waqd\pfile\initwaqd.ora"
>CREATE DATABASE waqd
>LOGFILE GROUP 1 ('d:\oracle\oradata\waqd\redo_01_a.log',
> 'd:\oracle\oradata\waqd\redo_01_b.log') SIZE 4096K,
> GROUP 2 ('d:\oracle\oradata\waqd\redo_02_a.log',
> 'd:\oracle\oradata\waqd\redo_02_b.log') SIZE 4096K,
> GROUP 3 ('d:\oracle\oradata\waqd\redo_03_a.log',
> 'd:\oracle\oradata\waqd\redo_03_b.log') SIZE 4096K
>MAXLOGFILES 30
>MAXLOGMEMBERS 3
>MAXLOGHISTORY 1
>DATAFILE 'd:\oracle\oradata\waqd\system01.dbf' SIZE 264M REUSE
>AUTOEXTEND OFF
>MAXDATAFILES 254
>MAXINSTANCES 1
>CHARACTER SET WE8ISO8859P1
>NATIONAL CHARACTER SET WE8ISO8859P1;
>spool off

The BEQueath protocol isn't compatible with Microsux Terminal Server, and Oracle has no intention fixing this, as Microsux Terminal Server is the only product with this problem.

You'll need to save your script, fire up a command window, issue set local=<tns servicename>
and do whatever you want in sql*plus.

A fellow victim

Sybrand Bakker, Senior Oracle DBA

To reply remove -verwijderdit from my e-mail address Received on Wed May 07 2003 - 12:30:36 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US