| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Export of Tables with lower case characters in the name.
No that wasn't the problem as it happens but I have got over it now anyway.
Regards
> Lee Robertson
> Acxiom
> Tel: 0191 525 7344
> Fax: 0191 525 7007
> Email: lerobe_at_acxiom.co.uk
>
-----Original Message-----
From: David Barbour [mailto:dbarbour_at_connectsouth.com]
Sent: 19 January 2001 16:31
To: Multiple recipients of list ORACLE-L
Subject: RE: Export of Tables with lower case characters in the name.
Oooh - I didn't think about having two tables with the same name differentiated only by upper and lower case. That would be a bad thing that shouldn't be allowed to happen! Is that part of your problem Lee? Otherwise, at first glance, Hitarth's script looks like it would work.
David A. Barbour
Oracle DBA - ConnectSouth
512-681-9438
dbarbour_at_connectsouth.com
-----Original Message-----
Sent: Friday, January 19, 2001 9:56 AM
To: Multiple recipients of list ORACLE-L
Lee,
I don't know if you tried this one yet, but since I've seen you strike out
several times now, I went over to Metalink and found this. Hopefully it will
help you out.
RDBMS Version: 8.1.5
Operating System and Version: Solaris 2.6
Error Number (if applicable):
Product (i.e. SQL*Loader, Import, etc.): Export
Product Version:
Exp does not discrimate table's name in lowercase and uppercase
I have in my TEST schema two tables named: "A" and "a", they were created by TEST user as follow:
create table "A" ("A" number);
create table "a" ("a" number);
I tried to export these tables using the following parfile:
userid=test/test
file=test
direct=y
tables=("a","A")
and got the next message:
About to export specified tables via Direct Path ...
. . exporting table A 0 rows exported
Export terminated successfully without warnings.
Exp does not discrimate table's name in lowercase and uppercase.
I also tried to change doble quote for single quote but I didn't have succeed. Does somebody know how to export them using tables parameter?
uppercase
This seems to work:
tables=(\"a\","A")
Unfortunately, this only seems to do the trick when using a parfile, if I do it at the prompt the backslashes will only discriminate in 7.3.4 and not 8.1.6!
uppercase
Rick is right, and it does work in 8.1.6. The double quotes are only needed around the lower case tablename. By default we will look for the tablename in upper case.
In my test, I used the following parfile:
tables=(\"a\", A)
This worked:
Connected to: Oracle8i Enterprise Edition Release 8.1.6.2.0 - Production
With the Partitioning option
JServer Release 8.1.6.2.0 - Production
Export done in US7ASCII character set and US7ASCII NCHAR character set
About to export specified tables via Conventional Path ...
. . exporting table a 0 rows exported
. . exporting table A 0 rows exported
Export terminated successfully without warnings.
Reem Munakash
Electronic Support
uppercase
Thanks a lot guys...
It is working fine...
Michael Ray
Oracle DBA
TRW, Marshall, IL
217-826-3011 x2438
-- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: David Barbour INET: dbarbour_at_connectsouth.com Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, pleaseReceived on Fri Jan 19 2001 - 11:07:42 CST
 |
 |