Select failover ORA-25401 when data is imported from an export on a RAC cluster
Date: Wed, 11 Jun 2008 21:00:51 -0700 (PDT)
We were told by consultants that on our production 2 node cluster (64-bit RedHat linux, RAW using ASM) database that after importing data into a new schema, the select failover was not functioning.
The data was imported into a new schema in a clustered db instance (2nodes). A huge select statement was run and a node was taken down to test select failover. Once the node was taken down the select statement issued the following message:
"ORA-25401 can not continue fetches" when selecting from a table from 1 node, and shutting down node to test failover selects.
The TAF looks like:
(ADDRESS = (PROTO = TCP)(HOST = oraclea1-vip)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = oraclea2-vip)(PORT = 1521)) (FAILOVER = yes) (LOAD_BALANCE = yes) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = IUAT_TAF1.ascendanalytics.com) (FAILOVER_MODE = (TYPE = SELECT) (METHOD = BASIC) (RETRIES = 180) (DELAY = 5))))
To get this to work, we had to import the data into a temporary schema, then from the real schema we want, we did a create table xxx as ... from the temp schema we imported the data into.
Thanks again for any suggestions.
I also have an attachement of the scr if you are interested. Doesn't look like I'm allowed to post attachments.
I have a issue, that I am going to be researching in detail and
> thought I'd run it by all as to the best way to test or if there is
> already a solution get it :) We were told by consultants that on our
> production 2 node cluster (64-bit RedHat linux, RAW using ASM)
> database that after importing data into a new schema, the select
> failover was not functioning.
> Has anyone had this same issue? If so what was your solution?
> I was planning on creating the user first and skeleton schema then
> importing only data via one of the nodes not the taf service.
> Any assistance as always is most welcomed.