Case sensitivity during data export

Hello all,
I have a question. During an export, all the members codes are exported in capital letters even if in the admin tool there is a small letter.
Do you know if there is an option that can be used in transformation file to avoid this conversion ?
Thanks
Eric

No, This can not be controlled, since BPC stores all the fact tables with capitalized values by itself.
Karthik AJ

Similar Messages

Avoiding case-sensitivity during reflection calls

Hi All,
I am reflecting methods from an object using java.lang.reflect.* classes and trying to invoke methods on the object. The problem is, I am aware of the filed names in the class that is reflected. The setter method name is not known exactly. They appear something like set<filed name>. Is there a way to avoid case sensitivity while trying to look up for methods from the class.
Any early help is highly appreciated.
Thanks
Varaga

You may also find java.beans.Statement and Expression useful:
public class CrappyBean {
    private int value;
    public void makeValue(int value) {
        this.value = value;
    public int findValue() {
        return value;
import java.beans.Statement;
import java.beans.Expression;
public class StatementUse {
    public static void main(String[] args) throws Exception {
        CrappyBean object = new CrappyBean();
        Statement setter = new Statement(object, "makeValue", new Object[]{17});
        Expression getter = new Expression(object, "findValue", null);
        setter.execute();
        System.out.println(getter.getValue());
}

Oracle Passwords CASE Sensitive

My Oracle 9i DB is not CASE sensitive on my passwords. I can not find any info on what parameter I can change to make it case sensitive.
All documents I find on net tell me that Oracle is CASE sensitive by default why are my passwords not?
Thanks in advance for any and all help,
David Miller

The topic they are typically were talking about being case sensitive is data insdie oracle db...
Also saw discussiona on use of " " (double quotes) on the ALTER USER command and password to make it specific to case.. Not sure where that came from at all...
Miller

How can I backup data from a case-sensitive volume to a NON-case-sensitive volume?

The case-sensitive volume in this instance being a desktop-mounted disk image volume.
A tragi-comedy in too many acts and hours
Dramatis Personae:
Macintosh HD: 27" iMac 3.06GHz Intel Core 2 Duo (iMac10,1), 12 GB RAM, 1 TB SATA internal drive
TB1: 1 TB USB external drive
TB2: 2 TB USB to Serial-ATA bridge external drive
Terabyte: a .dmg disk image and resulting desktop volume of the same name (sorry, I don't know the technical term for a .dmg that's been opened, de-compressed and mounted -- evanescently -- on the desktop)
Drive Genius 3 v3.1 (3100.39.63)/64-bit
Apple Disk Utility Version 11.5.2 (298.4)
Sunday morning (05/08/11), disk utility Drive Genius 3's drive monitoring system, Drive Pulse, reported a single bad block on an external USB2.0 1TB drive, telling me all data would be lost and my head would explode if I didn't fix this immediately. So I figured I'd offload the roughly 300 GB of data from TB1 to TB2 (which was nearly empty), with the intention of reinitializing TB 1 to remap the bad block and then move all its data BACK from TB 2. When I opened TB1's window in the Finder and tried to do a straight "Select All" and drag all items from TB1 to TB2, I got this error message:
"The volume has the wrong case sensitivity for a backup."
The error message didn't tell me WHICH volume had "the wrong case sensitivity for a backup," and believe me, or believe me not, this was the first time I'd ever heard that there WAS such a thing as "case sensitivity" for a drive. I tried dragging and dropping some individual folders -- some of them quite large, in the 40GB range -- from TB1 to TB2 without any problem whatsoever, but the majority of the items were the usual few-hundred-MB stuff that seems to proliferate on drives like empty Dunkin' Donuts coffee cups on the floor of my car, and I didn't relish the idea of spending an afternoon dragging and dropping dribs and drabs of 300GB worth of stuff from one drive to another.
Being essentially a simple-minded soul, I had what I thought was the bright idea that I could get around the problem by making a .dmg disk image file of the whole drive, stashing it on TB2, repairing and re-initializing TB1, and then decompressing the disk image I'd made of TB1, and doing the "drag and drop" of all the files in resulting desktop volume to TB1. So I made the .dmg of TB1, called "Terabyte," stashed that .dmg on TB2 (no error messages this time), re-initialized and then rebooted the iMac from my original Snow Leopard 10.6.1 disks and used Disk Utility to erase and initialize TB1 -- making sure that it was NOT initialized as case-sensitive, and installed a minimal system on TB1 from the same boot. Then I updated that 10.6.1 system to 10.6.7 with System Update, and checked to see that Disk Utility reported all THREE drives -- internal, 1TB, and 2TB -- as Mac OS Extended (Journaled), and no "case sensitive" BS. I also used Drive Genius 3's "information" function for more detailed info on all three drives. Except for the usual differing mount points, connection methods, and S.M.A.R.T. status (only the Macintosh HD internal, SATA 1TB drive supports S.M.A.R.T.), everything seemed to be oojah-***-spiff, all three drives showing the same Partition Map Types: GPT (GUID Partition Table.) Smooth sailing from here on out, I thought.
Bzzzzt! Wrong!
When I opened the Terabyte .dmg and its desktop volume mounted, I tried the old lazy man's "Select All" and drag all items from the desktop-mounted drive "Terabyte" to TB1, I got the error message:
"The volume has the wrong case sensitivity for a backup."
I then spent the next three hours on the phone with AppleCare (kids -- when you buy a Mac ANYTHING, cough up the money for AppleCare. Period.), finally reaching a very pleasant senior tech something-or-other in beautiful, rainy Portland, OR. Together we went through everything I had done, tried a few suggestions she offerred, and, at the end of three hours, BOTH of us were stumped. At least I didn't feel quite as abysmally stupid as I did at the beginning of the process, but that was all the joy I had gotten after two solid days of gnawing at this problem -- and I mean SOLID; I'm retired, and spend probably 12 hours a day, EVERY day, at the keyboard, working on various projects.
The AppleCare senior tech lady and I parted with mutual expressions of esteem, and I sat here, slowly grinding my teeth.
Then I tried something I don't know why I was so obtuse as to not have thought of before: I opened Apple's Disk Utility and checked the desktop-mounted volume Terabyte (Mount Point: /Volumes/Terabyte), the resulting volume from opening and uncompressing the .dmg "Terabyte".
Disk Utility reported: "Format : Mac OS Extended (Case-sensitive)." Doh!
Obviously, TB1, the 1 TB USB external drive I'd actually bought as part of a bundle from MacMall when I bought my 27" iMac, and which I had initialized the first day I had the iMac up and running (late November 2009), had somehow gotten initialized as a Case-sensitive drive. How, I don't know, but I suspect the jerk behind the keyboard. Whatever the case, when I created the Terabyte disk image (the drive's original name: when I erased and re-initialized it -- see above -- I renamed it "1TB" for quick identification), the original drive's "Case-sensitive" format was encoded too. So when I tried to drag and drop EVERYTHING from the desktop-mounted volume "Terabyte" to the newly initialized and "blessed" (now THERE's a term from the past!), the system recognized it as an attempt as a total volume backup, and hit me with "The volume [the desktop-mounted volume "Terabyte" -- BB] has the wrong case sensitivity for a backup." And, of course, the reinitialized TB1 was now correctly formatted as NOT "case-sensitive."
Well, that solved the mystery (BTW, Disk Utility identified the unopened Terabyte.dmg as an "Apple UDIF read-only compressed {zlib}, which is why the .dmg file could be copied to ANY volume, case sensitive or not), but it didn't help me with my problem of having to manually move all that data from the desktop-mounted volume "Terabyte" to TB1. I tried to find a way to correct the problem at the .dmg AND opened-volume-from-.dmg level with every disk utility I had, to no avail.
Sorry for the long exposition, but others may trip over this "case-sensitive" rock in the road, and I wanted to make the case as clear as possible.
So my problem remains: other than coal shovel by coal shovel, is there any way to get all the data off this case-sensitive desktop-mounted volume "Terabyte" and onto TB1.
Not that I know whether it would made any difference or not, one of the things that got me into this situation was my inability to get "Time Machine" properly configured so it wasn't making new back-ups every (no lie) 15 minutes.
Philosophical bonus question: what's the need for this "case-sensitive," "NOT case-sensitive" option for disk initialization?
As always, thanks for any help.
Bart Brown

"Am I to understand that you have a case-sensitive volume with data that you want to copy to a case-insensitive volume? And the Finder won't let you do it? If that's what the problem is, the reason should be obvious: on the source volume, you may have two files in the same folder whose names differ only in case. When copying that folder to the target volume, it's not clear what the Finder should do."
Yes, I understand all that... NOW.
What I had (have) is a USB external 1TB drive (henceforth known as "Terabyte") that I bought with my 27" iMac. I formatted, and put a minimal (to make it bootable) system on Terabyte the same day back in late November 2009 that I set up my 27" iMac. Somehow -- I don't know how -- Terabyte got initialized as "case-sensitive." I didn't even know at the time that there WAS such a thing as "case-sensitive" or "NOT case-sensitive" format.
Sunday morning (05/08/11), Drive Pulse, a toolbar-resident utility (that's Part of Drive Genius 3) that monitors internal and external drives for physical, problems, volume consistency problems, and volume fragmentation, reported a single bad block on the volume Terabyte, advising me that it would be best if I re-formatted Terabyte ASAP. I thought I could open Terabyte in a Finder window, Select All, and drag everything on the drive to ANOTHER USB external drive of 2 TB capacity (henceforth known as TB2). When I tried to do that, I got an error message:
"The volume has the wrong case sensitivity for a backup."
First I'd heard of "case sensitivity" -- I'm not too bright, as you seem to have realized.
Oddly enough (to me), I could move huge chunks of data, including a folder of 40GB, from Terabyte to TB2 with no problem.
Then the scenario unfolded per my too-convoluted message: several hours of trying things on my own, including making a .dmg of Terabyte (henceforth to be known as Terabyte.dmg) -- which left me with the exact same problem as described in the previous 4 paragraphs; and my 3 hours on the phone with AppleCare, who at least explained this case-sensitive business, but, after some shot-in-the-dark brainstorming -- tough to do with only one brain, and THAT on the OTHER end of the line -- the very pleasant AppleCare rep and I ended up equally perplexed and clueless as to how to get around the fact that a .dmg of a case-sensitive volume, while not case-sensitive in its "image" form (Terabyte.dmg), and thus able be transferred to TB1 or TB2 with no problems whatsoever, when opened -- either by double-clicking or opening in Disk Utility -- produced a desktop-mounted volume (henceforth known as the volume "Terabyte," the original name of the case-sensitive volume from which TB1.dmg had been made) that had the same case-sensitivity as the original from which it was made.
In the meantime, having gotten the data I needed to save off the physical USB "case-sensitive" volume Terabyte in the form of Terabyte.dmg, I erased and re-initialized the physical USB "case-sensitive" volume Terabyte, getting rif of the case sensitivity, and renaming it TB1. But it all left me back at square one, EXCEPT I had saved my data from the original "Terabyte" drive, and reformatted that drive to a NON- case-sensitive data now named TB1. The confusion here stems from the fact that problem case-sensitive drive, from which I made Terabyte.dmg, was originally named "Terabyte". When I re-initialized it as a NON case-sensitive drive, I renamed it TB1. I'm sorry about the confusing nomenclature, which I've tried to improve upon from my original message -- usual text-communication problem: the writer knows what he has in mind, but the reader can only go by what's written.
So, anyway, I still have the same problem, the desktop-mounted volume "Terabyte" still cannot be transferred in one whole chunk to either my internal drive, TB1, TB2, as the Finder interprets it as a volume backup (which it is), and reads the desktop-mounted volume "Terabyte" as case-sensitive, as the original volume -- from which the disk image Terabyte.dmg was made -- had been at the time I made it.
"As long as that situation doesn't arise, you should be able to make the copy with a tool that's less fastidious than the Finder, such as cp or rsync."
I'm afraid I have no idea what "cp or rsync" are. I'd be happy to be educated. That's why I came here.
Bart Brown
Message was edited by: Bartbrn
Just trying to unmuddy the water a bit,,,

How do i reformat a case sensitive external hard drive without losing data

I know there are a lot of posts about this, and i have spent hours trying to find a soloution / understand what people have responded to others, but i can't work this out.
I also have a Buffalo HD (let's call it HD1) that stores my itunes library.
I have a WD My Passport for Mac (let's call it HD2) that backs up my Mac Book Pro.
I have an older WD that has older TM back ups on it from previous computers (let's call it HD3)
I have one spare completely 'clean' WD hard drive (let's call it HD4).
My laptop was really slow and full so i went to Genius bar, they sold me the Buffalo HD and they moved my itunes to it and set it up so it now has my itunes. I used this disk to run two TM Backups before i realised the drive was nearly full, so i bought the WD My Passport HD2.
I now use WD My Passprt HD2 for TM.
I want to MOVE the backups on HD1 to My Passport HD2 as there is lots of space on it. I also want to move my itunes library from HD2 as a back up.
But i can't!!!
After reading for hours, apparently this is because my HD1 is case sensitive, journaled. And it needs to be Journaled to work with TM/OSX or something very confusing. I have read lots of threads about re-formatting / partitioning and all things that are way over my head. But the one thing i do understand is if i reformat HD1, it erases the data.
This is NOT an option as it holds my WHOLE itunes. The Itunes is WAY too big to drag onto my mac book pro and then move it over to HD2 and make that my itunes folder.
HOW THE **** ARE YOU SUPPOSED TO BACK UP THE CASE SENSITIVE DRIVE BEFORE REFORMATTING IT IF IT'S TOO BIG TO FIT BACK ON YOUR COMPUTER? Surely that's the whole point of having an external drive... to back up AND give you more space?
I'm so mad that the apple store did this to me... they should know that case sensitve wouldn't work with a passport... that i would have problems. UGh.
I have options to move the files from HD1 as i have HD2 and HD3 and then also the completely unused HD4... but i can't move anything anywhere due to this case sensitive nightmare.
Someone PLEASE HELP ME.
thanks.

Hi Kappy,
Just wondering if you had any advice for my situation . . .
My time machine backup was backing up to a drive that was "Mac OS X Enteded Journaled, Case Sensitive." I had no idea what this meant, or that it would even cause issues.
I took my computer to the Apple store yesterday, and they wiped it clean. When they tried to restore it from the Time Machine backup drive, it would not work. Their guess is that Time Machine cannot restore from a drive that is "case sensitive."
Any thoughts on how I can convert my time machine backup data from a "case sensitive" state, to a "non-case sensitive" state? I've tried to just drag and drop the files from the case sensitive formatted drive to a new drive that I have that is formatted non case sensitive, but I get the following error message:
"The volume has the wrong case sensitivity for a backup"
I just really want my data back - I thought TimeMachine was the way to go (and was supposed to work) but unfortunately it is not.
Any help you can provide would be greatly appreciated.
Thanks,

Hibernate for lower case data(case sensitive) in oracle 10G

Hi,
I generated my data (oracle 10G release 2) using lowercase data types and table names. This requires queries in the strict form of -
Select "Column_Name" from "Table_name";
But Hibernate makes the queries as -
Select Column_Name from Table_Name;
driver I am using is oracle.jdbc.driver.OracleDriver
Jar is ojdbc14
and dialect is org.hibernate.dialect.Oracle9Dialect
The problem is:
table or view does not exist.
as it(lower case data) does not recognize the hibernate query format.
Can anyone suggest the proper driver and Jar to overcome the problem.
Regards,
Ankit

Ankit,
Just bite the bullet and don't use case-sensitive identifiers :-)
I don't use "hibernate", but maybe you can add the double-quotes -- " -- in the XML file?
I don't think there's a JDBC driver that adds the double-quotes for you. So I think your only option (if you insist on using case-sensistive identifiers) is to explore possibilities through "hibernate" itself.
I also don't think there's any database setting that allows Oracle to accept case-sensitive identifiers.
Good Luck,
Avi.

Case sensitive data in workflow

I am working with some case sensitive data in a work flow. To set and get the values from the container, I am using the macros swc_set_element and swc_get_element.
I realized that these macros automatically convert the case of the data I am passing to upper case. I don't want the case conversion to happen, and want to retain the original case of the data (which is a mix of upper and lower case).
Can somebody suggest an approach to handle the same?? Its kinda urgent.
Thanks,
Srihari

Hi,
The data is generally converted to Uppercase if the Domain of the data you are using is not marked as case sensitive. You can set the "Lowercase" check box for the respective domains so that data is maintained in a case sensitive manner. May be you can copy the code of these macro's and change them to use your own case sensitive domains.
Regards,
Sesh
Message was edited by:
Seshatalpasai Madala

Selecting the data without considering any case sensitives

Moderator message: please do not post the same question more than once
Hi,
I need to select the data without considering any case sensitives.
Eg: If i enter ***JoHn****, then system need to select all currencies or amount depending on the this name.
Please assist, many thanks.
Sameer.
Edited by: Matt on Nov 20, 2008 1:16 PM

Hi,
use cp or like in the select query
and more over any thing given in single quotes must be in upper case to my knowledge in ABAP.
any how try this
select * from dbtab where name like '%JoHn%'.
if doesnt work translate it to upper case.
hope this this would solve.
regards
Ramchander Rao.K

Case sensitive data

Hi,
Running on MS-SQL and creating a user defined field is it then possible to set collation to CS instead of default CI (Case Insensitive).
Of course you can always do this from EM, but when patching the database this setting will be lost.
I've noticed when creating a new company the collation of database will be set to "SQL_Latin1_General_CP850_CI_AS".
Is there anyway to change default collation to "SQL_Latin1_General_CP850_<b>CS</b>_AS" ??
Soren

Well, I need to do this as some of my data is case sensitive
Say: AAABCI differs from AAABCi
And yes, when patching a SBO with a CS key field on a user defined table will course the pathing to fail.
The data is imported from a remote system (R3) and is crutial for a series of add-ons using this master data.
There is no way of doing direct queries in the remote system.

Error 22 case sensitive volume during installation - how to change install drive?

I want to install Creative Cloud on my Mac but get the Error Code 22 for a case sensitive volume. It says I should choose a different volume to install but doesn't offer any way to choose the installation volume. How to I tell the installer to use my 2nd harddrive instead of my system drive?

Case sensitive hard drive
http://helpx.adobe.com/creative-suite/kb/error-case-sensitive-drives-supported.html

Case Sensitivity for 8i 8.1.7

Hello everyone,
I have noticed after my wonderful install of 8i (8.1.7 EE) all of my tables, fields, and so on are upper case names. I know I can use the " to create/specify an object by its' case (say lower case instead of upper). When I run queries through an ODBC driver. My data is returned all in upper case (because all of my objects are upper?). Is there an option during or post installation that I can throw for case insensitive on all of my objects? When I create a new table using the UI tools and wizards. I want the default to be lower case not upper case. Even when I use the MS SQL 2k export wizard to oracle. All of my objects are upper case. I know during a MS SQL install you can select you case sensitivity option. I would like to know how to do this in oracle, thanks.
Jason Jennings
[email protected]

There is no case-sensitive option in Oracle that I know of. Unless you specify thing in double-quotes when you creaet it (eg. create table 'MyTable') everything in Oracle is stored in upper-case as far as the data-dictionary is concerned.

Essbase Data Export not Overwriting existing data file

We have an ODI interface in our environment which is used to export the data from Essbase apps to text files using Data export calc scripts and then we load those text files in a relational database. Laetely we are seeing some issue where the Data Export calc script is not overwriting the file and is just appending the new data to the existing file.
The OverWriteFile option is set to ON.
SET DATAEXPORTOPTIONS {
     DataExportLevel "Level0";
     DataExportOverWriteFile ON;
DataExportDimHeader ON;
     DataExportColHeader "Period";
     DataExportDynamicCalc ON;
The "Scenario" variable is a substitution variable which is set during the runtime. We are trying to extract "Budget" but the calc script is not clearing the "Actual" scenario from the text file which was the scenario that was extracted earlier. Its like after the execution of the calc script, the file contains both "Actual" and "Budget" data. We are not able to find the root cause as in why this might be happening and why OVERWRITEFILE command is not being taken into account by the data export calc script.
We have also deleted the text data file to make sure there are no temporary files on the server or anything. But when we ran the data export directly from Essbase again, then again the file contained both "Actual" as well as "Budget" data which really strange. We have never encountered an issue like this before.
Any suggestions regarding this issue?

Did some more testing and pretty much zoomed on the issue. Our Scenario is actually something like this "Q1FCST-Budget", "Q2FCST-Budget" etc
This is the reason why we need to use a member function because Calc Script reads "&ODI_SCENARIO" (which is set to Q2FCST-Budget) as a number and gives an error. To convert this value to a string we are using @member function. And, this seems the root cause of the issue. The ODI_Scenario variable is set to "Q2FCST-Budget", but when we run the script with this calculation function @member("&ODI_SCENARIO"), the data file brings back the values for "Q1FCST-Budget" out of nowhere in addition to "Q2FCST-Budget" data which we are trying to extract.
Successful Test Case 1:
1) Put Scenario "Q2FCST-Budget" in hard coded letters in Script and ran the script
e.g "Q2FCST-Phased"
2) Ran the Script
3) Result Ok.Script overwrote the file with Q2FCST-Budget data
Successful Case 2:
1) Put scenario in @member function
e.g. @member("Q2FCST-Budget")
2) Results again ok
Failed Case:
1) Deleted the file
2) Put scenario in a substitution variable and used the member function "@member("&ODI_Scenario") and Ran the script . *ODI_SCENARIO is set to Q@FCST-Budget in Essbase variables.
e.g. @member("&ODI_SCENARIO")
3) Result : Script contained both "Q1FCST-Budget" as well as "Q2FCST-Budget" data values in the text file.
We are still not close to the root cause and why is this issue happening. Putting the sub var in the member function changes the complete picture and gives us inaccurate results.
Any clues anyone?

Mac OS X, User Folder and Case-sensitivity (plus a Partitioning Question)

Hello everybody.
Today, I'd like to start a new thread regarding the configuration of OS X and the formatting of the drive with a HFS+ (case-sensitive, journaled) file system.
There is a problem that has been tormenting me for quite some time now, and so far I haven't been able to find a losution yet.
Here is the issue. When I bought my MacBook Pro (early 2011), I changed the main dirve to an hybrid SSD destinating the original 750GB to a Time Machine backup disk. As a consequence I had to make a fresh install of OS X. When it came the time of formatting I've opted for:
Creating two partitions: 1 for the OS and 1 for the user folder (I have only one admin-user). Back then, I was coming from a Win enviroment and having two partitions seemed to be the best option for me. (Less chanche of user-data corruption in case something goes wrong in the OS partition).
Chose a HFS+ (case-sensitive, journaled) file system. It seemed to be the more complete alternative.
Everything was absolutely for a couple of months then I encountered the first issue: Adobe products don't work on a case-sensitive fs.
I managed to get Photoshop to work eventually (manually correcing folders name) and didn't care too much about the rest.
In the meantime over a year has passed and I kept the mentioned configuration, uptdating to Lion and ML. Recently another couple of isses have appeared: AutoCAD presents the same problem as Adobe and there is an issue in the keyboard balcklight control (from forums seems that ML is not able to store any information in System Preferences regarding the backlight).
Despite the fact that case-sensitive fs seems to be the future solution chosen by Apple, it is still premature to have it as OS fs unless you are an hard-core developer that don't care about tons of programs that would eventually miss from your application folder.
Being decided to move back to a case-insesntive fs, I need wish I could calrify a couple of doubts before proceding:
(Not relatete to fs) Is it a good practice to keep user folder on a separate volume? Does it generates any issue on the base of your experience?
Is it possible to have the OS on case-insensitive fs and the user folder on a case-sensitive one? Does the OS have an issue with that?
The second point is the most critical as my data are now on a case-sensitive volume. They mostly consists in documents, images and music which should be migrated on a case-insensitive volume seamlessy, however, I'm not 100% sure about what happened during the last year (i.e. if there has been the generation of not-unique names).
Furhtermore, I wish I could keep a case-sens volume as I plan to be dealing with a Linux enviroment soon. If that could be the user volume, this would be amazing.
I'd also like to ask personal opinion on advantages of having case-sens fs.
I understand I asked lots of questions in a single post. I hope, however, that this thread could be a base to collect some of the quite dispersive topics related to case-sensitivity present on the web.
Best Regards,
Alexander

alexanderxc wrote:
Linc, in the provious post you said there might be issues having user data on a separte partition.
Which kind of issues are you tihnking of? Have you ever encountered such problems?
The biggest risk is that poorly written software will assume your home directory is at /Users/you and will fail (or worse) if it doesn't like what it finds there.
I really appreciated if you could be more specific and don't worry about being too technical.
There are two ways you can go about it.
1) Set everything up normally as if you only had one partition. Create your user on that one parition. Then, copy all the real user data to the 2nd partition. Using your admin account, make sure that all the permission on the user folder on the 2nd partition are the same as on the original partition. The, use System Preferences > Users & Groups > your account > right/control click > Advanced > Home directory and change it to the home directory on the 2nd partition. Log in to that new account. Make sure everything works. Then delete the user directory at /Users.
2) A even more robust, old-school option is to create an /etc/fstab file and have your 2nd partition mounted at /Users. Then, everything will function normally and your user home directories will all be at /Users. /Users will, however, be on a different volume.

Query in expdp with case-sensitive table and columnname

Hi,
I've got a problem with exporting some specific rows of a table.
The problem is a case-sensitive table and column name. I've tried this in a parfile:
dumpfile=dpumpdir1:test.dmp
logfile=dpumpdir1:test.log
tables="Data"
query="Data":'"where "DataID" = 11"'
but it ended like this:
ORA-31693: Table data object "Data" failed to load/unload and is being skipped due to error:
ORA-06502: PL/SQL: numeric or value error
ORA-31605: the following was returned from LpxXSLSetTextVar in routine kuxslSetParam:
LPX-314: an internal failure occurred
Edited by: [Logik on 18.04.2013 01:18

I've tried to make a function with this. I think you used some Oracle 11 parameters. reusefile for example.
However I've managed to compile the function without error:
CREATE OR REPLACE FUNCTION EXPDP RETURN NUMBER IS
h1 number;
v_job_state       varchar2(4000);
BEGIN
h1 := dbms_datapump.open(operation=>'EXPORT',job_mode=>'TABLE',job_name=>'HARRY10');
dbms_datapump.add_file(h1,'example1.dmp','DPUMPDIR1');
dbms_datapump.add_file(h1,'example1.log','DPUMPDIR1',filetype => dbms_datapump.ku$_file_type_log_file);
dbms_datapump.metadata_filter(handle => h1,name => 'NAME_EXPR',value => 'IN (''Data'')',object_type => 'TABLE');
dbms_datapump.data_filter(handle => h1,name => 'SUBQUERY',value => 'WHERE "DataID" = 1');
dbms_datapump.start_job(h1);
DBMS_DATAPUMP.WAIT_FOR_JOB (h1,v_job_state);
DBMS_OUTPUT.PUT_LINE(v_job_state);
RETURN NULL;
END EXPDP;But when I execute I get:
ORA-31626: job does not exist
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79
ORA-06512: at "SYS.DBMS_DATAPUMP", line 938
ORA-06512: at "SYS.DBMS_DATAPUMP", line 4592
ORA-06512: at EXPDP", line 5
ORA-06512: at line 5
Probably not my day :(
By the way... how can I Format the text as a script?
Edited by: [Logik on 19.04.2013 11:01

Case sensitive in Function Module

Hi experts,
we created the custom table and maintaining the data.we saved the data with key as case sensitive which we selected at domain level .we created custom function module in that we have written SELECT statement with where clause .when we are testing the function module in SE37 ,if i enter lower case value in the exporting parameters and after executing the F.M the input values are changing into upper case. so i am getting wrong data.please help me.

Hi Vinod,
I have given interface import parameter reference Z-data element which is already used in the Z-table.For example In the FM
iv_name type zz_name.
zz_name is a data element and ZZ_NAME1 is domain name and where i selected the check box as lower case and upper case.
Please any one help me.

Case sensitivity during data export

Similar Messages

Maybe you are looking for