Some of you may recall a question I posted on a problem with MTS connection
pooling. MTS continued to try to connect to our old IP address after
switching between production and standby. This happened even though we
switched the IP address the DNS Name was pointing to.
Well, we finally managed
Sorry, I've never used MS-MTS...
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Monday, May 20, 2002 3:48 PM
> Thanks,
>
> We tried this syntax in our test environment and it worked very well but
of
> course had no way of knowing if it solved o
Thanks,
We tried this syntax in our test environment and it worked very well but of
course had no way of knowing if it solved our problem since that didn't show
up in the test environment even in normal circumstances.
Have you actually had experience using this when Microsoft Transaction
Server w
prod = (description=
(address_list=
(failover=ON)
(load_balance=OFF)
(address=...) <= points to primary db
(address=...) <= points to standby db
)
(conn
When we switch between production and standby databases our procedure is to
change the DNS Name to point to the new ip address.
This works perfectly for all our old Powerbuilder client/server apps.
However, our connections that go through Microsoft Transaction Server as a
middle tier apparently c
I got this error when I first set up my standby database. If you generate a
log switch, and then recover again you will not see the problem. If I
recall correctly, the issue arises when the redo log that was active when
you created your standby control file has not been archived. If you issue a
Janet,
I have found that on NT a shutdown immediate can still lead to recovery being required
when the database is started back up.
That is, maybe you didn't really have a consistent cold backup of your primary.
I have instead opted for a shutdown immediate, startup, shutdown normal sequence to
Hi,
I created a primary and a standby database. Both are
9i on Win2000, the same host. Everything was fine,
except the last step:
SQL> RECOVER MANAGED STANDBY DATABASE TIMEOUT 20;
ORA-01547: warning: RECOVER succeeded but OPEN
RESETLOGS would get error below
ORA-01152: file 1 was not restored
Title: Standby Database Problem
Hussain,
As long as none of your datafiles were corrupted by
what I assume was the crash of your Standby Instance, you can reinstall 8i and
bring up the Standby just as you describe. The datafiles don't care at all
where Oracle Home is.
I recently h
Title: Standby Database Problem
Hi
While trying to install developer6 on our standby database test server (OS NT4, Oracle 8.1.7), I have some how corrupted the 8i, and hence the standby database is not working. Its actually the Oracle Suite tools which are not working. I am going to
10 matches
Mail list logo
