Determing DBA vs IMP_FULL_DATABASE in 9i vs 10g

Question

Is there a difference between 9i and 10g in the way they each determine whether a user has DBA with regards to importing an export that was exported by a DBA user?
The reason I ask, we have an export that was taken from a 9i database using a 9i client where the user had the DBA role. When we go to import this file we are successful importing using a user that only has connect and im_full_database IF we are importing into a 10g database. If we try importing into a 9i database with a user having just those same 2 roles, we get the error: IMP-00013: only a DBA can import a file exported by another DBA
This is expected but I was curious about the fact that 10g seems to be a little more lenient with regards to whether the importing user is a DBA than 9i is.
Were there any known changes to this feature between 9i and 10g?
Tina

Answer 1

Yes, actually I did and it was successful. At the time I posted I had only tried it importing into a 10g database so I was taking our customers word for the fact that it didn't work.
But you are correct... I installed 9i client and imported into a 9i database and it works fine for me as well. I'm having the customer check nls settings on the client, even though I don't know why that would give a 013 error.
I've just been told that the customer does have access to a DBA user on the database so why he is not just using that and going forward I do not know. Admittedly it is an odd problem but it could be something unique to that particular database.
The export file does have raw data types in it. It also has a date column and some number columns but none of the actual number values have decimals. (thus my thoughts towards the nls settings for number)
NUMBER(9)
VARCHAR2(80)
VARCHAR2(80)
RAW(2000)
RAW(2000)
NUMBER(1)
DATE
NUMBER(9)
This is the command the customer used to create the user to import with. Let me know if you see anything that stands out that might be causing a problem. One of our other engineers says she tried this exact command to create a user and then used it to import successfully, but I did not try it myself.
CREATE USER TEST
IDENTIFIED BY VALUES '7A0F2B316C212D67'
DEFAULT TABLESPACE GNET
TEMPORARY TABLESPACE TEMP
PROFILE DEFAULT
ACCOUNT UNLOCK;
-- 2 Roles for TEST
GRANT CONNECT TO TEST;
GRANT IMP_FULL_DATABASE TO TEST;
ALTER USER TEST DEFAULT ROLE NONE;
-- 1 System Privilege for TEST
GRANT CREATE SESSION TO TEST;
-- 2 Tablespace Quotas for TEST
ALTER USER TEST QUOTA UNLIMITED ON TEMP;
ALTER USER TEST QUOTA UNLIMITED ON GNET;
Thanks so much for your responses,
Tina