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.

Similar Messages

  • Case sensitivity for comparisons

    It appears that text comparisons on rules are case sensitive?
    In other words the rule:
    the cow gives milk is valid if
    the cow's name = "Betsy"
    will not be valid if the cow's name is "BETSY"...
    Assuming that is correct, how do people handle case sensitivity for text fields in OPA? I don't see a toupper() for text.

    It appears we answered our own question when it was pointed out that the example in developer documentation on extensions was for this very problem...

  • The volume has the wrong case sensitivity for a backup

    Updated to OS X Yosemite 10.10.1 and when trying to restore my backup (using TM) into my iMac (27-inch, Mid 2011) get the following message: "The volume has the wrong case sensitivity for a backup."
    Any help would be appreciated!

    That's not how you restore.
    Move your data to a new Mac - Apple Support
    OS X Yosemite: Recover your entire system

  • My Time Machine backup keeps failing.  I get a message the "Volume has the wrong case sensitivity for a backup".  Please advise.

    My Time Machine backup keeps failing.  I get a message the "Volume has the wrong case sensitivity for a backup".  Please advise.
    Thanks, Howard

    You can change the case sensitivity of the sparsebundle.. but I really doubt the error is real.
    See A8 here.
    http://pondini.org/TM/Troubleshooting.html
    The sparsebundle should have case sensitivity turned on.
    I cannot even fathom how it could have changed.
    Let me recommend before you start fooling around with the sparsebundle.
    Do a full network start.
    Power everything off.. start up modem.. wait 2min.. power up the TC.. wait 2min.. power up any other network gear like switches.. wait..
    Now power up the computer and try it.
    If the error is the same.. I would do a factory reset of the TC.. give it all short names, no spaces and pure alphanumeric. Then reset TM .. see A4 in the same reference as above.. and do a verify of the backups.. A5 above and try the backup again..
    No luck..
    Then erase the TC and start over.. it is sometimes necessary as TM does get itself in a knot.

  • Case sensitivity for text fields

    Does anyone know how to turn off case sensitivity for a text field??
    Your help is appreciated.

    Do you recommend another field type that can be used that does not use case sensitivity?
    Thank you

  • How to Configuring case sensitivity for NFS on Windows Server 2012

    Configure Case Sensitivity for File and Folder Names
    http://technet.microsoft.com/en-us/library/cc725747.aspx
    To configure case sensitivity for file and folder names using the command prompt             
    Open a command prompt.
    To enable case sensitivity, type:
    nfsadmin server [ComputerName] config casesensitivelookups=yes
    But, "casesensitivelookups" is removed in Windows 2012 version.
    Help Me~

    Hi,
    Sorry for the delayed response.
    According to the following article, we still can use
    nfsadmin to configure case sensitivity for Server for NFS in Windows Server 2012.
    Nfsadmin
    http://technet.microsoft.com/en-us/library/cc771599.aspx
    Note:We
    need to disable Windows kernel case-insensitivity in order for Server for NFS to support case-sensitive file names. We can disable Windows kernel case-insensitivity by clearing the following registry key to 0:
    HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\kernel
    DWORD “obcaseinsensitive”
    Hope it helps.
    Best regards,
    Frank Shen

  • Setting case sensitivity for text searches

    I am trying to figure out how to set case sensitivity for text searches for Oracle. I am using 8.1.7 and the documentation keeps referring me to the Basic_Lexer object. Does setting the mixed_case parameter to 'No' remove case sensitivity for the index or is there something else I need to do?

    Do you recommend another field type that can be used that does not use case sensitivity?
    Thank you

  • Disable Case Sensitivity for Node Names

    Hello everyone,
    is it possible to dissable the case sensitivity for node names?
    I have an import of ca. 40k records. The source system differs between small and capital letters.
    DRM seems to not differ between small and capital letters.
    Is there a workaround without usind different technical names for nodes.
    Kind regards,
    Pascal

    There is nothing to do with in DRM, can you check with your DBA on what's the NLS_SORT and NLS_COMP settings are,ask them to check the below values.
    NLS_COMP=LINGUISTIC and NLS_SORT=BINARY_CI
    If nothing works out submit an SR:-)

  • Turn off case sensitive for whole system

    Hello,
    I am looking for the feasibility to turn off the case sensitive functionality for the whole system. Is it ever possible?
    Thank you in advance.
    Dmitri

    Dmitri, at this time it is not possible to turn off the case sensitive functionality. I would recommend that you submit a enhancement request to CRM On Demand customer care.

  • Change volume to non case sensitive for Time Machine?

    I need to back up a drive I use to archive material.  Tried to add it to list of drives time machine backs up.  Found out the external drive was set up as case sensitive (must have been a default out of the box, never made this choice).  Is there any way to tell an external drive "don't be case sensitive" so that I will be able to back it up with Time Machine?  (That is, make the case sensitive change to the drive without erasing the drive!)  Simpler way to ask question, how can I back up an exernal drive using Time Machine if that external drive was set up as case sensitive?  Thanks in advance

    Glenn Carter wrote:
    Unfortunately, an Erase and Install is probably the only way you are going to fix this. As you have discovered, it appears that "Restore System From Backup..." reformats the destination drive to match the state in which the backups took place.
    The TM backup may not have the ability to rename dupes that might occur if some files have identical names save their case.
    Even a reformat and reinstall may not work unless any pseudo-identical files are first renamed.

  • HT1553 My motherboard failed and was replaced at the Apple store but I did not have my backup with me for the tech to download. When I try to download, a window comes up that the volume has the wrong case sensitivity and will not download. Thank you for a

    I did not have my backup with me when my hard drive failed and was replaced at the Apple store. Now it will not download to my new hard drive. A message says that "the volume has the worng case sensitivity for a backup". How can I resore my data from the backup?
    Thank you

    This is a user-supported board. You are not addressing Apple here. Nor is it a good idea to post your private information to a public forum. You should edit your post immediately.
    Unfortunately no one here can access your support history. You must respond to the emails directly.

  • 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,

  • Case sensitivity in Oracle Text

    I am familiar with the mixed_case parameter, and in my setup it is set to no, so all searches are case-insensitive. This is what I want 95% of the time, but is there a way to specify (at a query level) that a contains search is case sensitive?

    Hi,
    Would be nice, but the tokens are converted to uppercase on indexing. For example:
    SQL> create table test (col1 varchar2(20));
    Table created.
    SQL> insert into test values ('MixEd cAsE');
    1 row created.
    SQL> create index test_idx on test(col1)
    2 indextype is ctxsys.context;
    Index created.
    SQL> select token_text from dr$test_idx$i;
    TOKEN_TEXT
    CASE
    MIXED
    So, since they are actually stored/converted to uppercase there is nothing case-sensitive for your query to compare to.
    On the flip side, if you index case-sensitive, the tokens are stored mixed-case.
    SQL> drop index test_idx force;
    Index dropped.
    SQL> begin
    2 ctx_ddl.create_preference('mylex', 'BASIC_LEXER');
    3 ctx_ddl.set_attribute('mylex', 'mixed_case', 'yes');
    4 end;
    5 /
    PL/SQL procedure successfully completed.
    SQL> create index test_idx on test(col1)
    2 indextype is ctxsys.context
    3 parameters('lexer mylex');
    Index created.
    SQL> select token_text from dr$test_idx$i;
    TOKEN_TEXT
    MixEd
    cAsE
    Now you can do something with your query to make it do what you want. You'd have to check performance to see if it is worth it.
    Ron

  • CSS cookieurl: case sensitive?

    Hello,
    As far as I understand, the HTTP header cookie field, and the embedded cookie (in a URL) are case-sensitive. Is this correct?
    The settings look like this:
    content stickyCookie
    advanced-balance cookieurl
    string prefix "SESSION_ID="
    On the HTTP header the cookie field looks like this:
    Set Cookie: SESSION_ID=ABCDEF
    But if instead of this, the request comes from a client with the cookie embedded in the url, it looks like this:
    http://localhost/Info/index;session_id=ABCDEF?page=home.
    Is this field case-sensitive for the CSS? I know it is for the ACE, as I have done this and there is the "cookie secondary" command where you can specify how the url-embedded cookie looks like.
    So I am afraid there is no way of making this work on a CSS?
    Any help will be much appreciated!

    Hi Javier,
    The Cisco CSS is case-sensitive when searching for this string.
    When configuring the CSS 11000 and 11500, determine first if you need a server cookie string. If the string operation under the content rule is match-service-cookie, which is the default setting, this parameter must be configured. In this case the service cookie string is matched against the cookie contained in the HTTP header for load balancing decision.
    If the string operation under the content rule is set to the hash method, this parameter is not needed. In order to select one of the available servers, the cookie contained in the HTTP header is mathematically processed using a hashing algorithm. If available, the hash algorithm assigna the connection carrying a certain cookie to the same server. This example focuses on the match-service-cookie case.
    Note: Cookies are case sensitive.
    Configuring the Service
    training4(config># service server_g
    training4(config-service[server_g])# string LV2KJK (the server cookie text)
    training4(config># service server_h
    training4(config-service[server_h])# string AARIKA
    Configuring the Content Rule
    Note: Cookies require a Layer 5 rule.
    You can create a Layer 5 rule by adding a URL.
    For example, .
    A Layer 4 rule can be promoted to a Layer 5 rule by issuing the advanced-balance cookies command.
    Choose the advanced-balance method.
    training4(config-owner-content[cookie-layer5])# advanced-balance cookies
    Configure the string operation.
    training4(config-owner-content[cookie-layer5])# string operation ?
    match-service-cookie (DEFAULT)
    hash-crc32
    hash-xor
    hash-a
    Define the starting/ending bytes.
    training4(config-owner-content[cookie-layer5])# string range 1 to 200
    Start byte position of cookie/url after header (Range:1-600)
    Specify the prefix located in the string range.
    training4(config-owner-content[cookie-layer5])# string prefix "ASPSESSION"
    "Quoted textual information"(Len: 0-32)
    Indicate how many bytes to skip after the starting prefix.
    training4(config-owner-content[cookie-layer5])# string skip-length 9
    "Quoted textual information"(Len: 0-32)
    Indicate how many bytes after the prefix/skip-length make-up the string.
    training4(config-owner-content[cookie-layer5])# string process-length 6
    Integer value(Range: 0-64)
    If no string process length is configured, search after end of string character.
    training4(config-owner-content[cookie-layer5])# string eos-char "&"
    "Quoted textual information"(Len: 0-5)
    Specify the failover in the event that a server goes down or is suspended.
    training4(config-owner-content[cookie-layer5])# sticky-serverdown-failoversticky-srcip
    sticky-srcip-dstport
    sticky-srcip
    balance (Default)
    redirect
    reject
    Below is an example of a cookie string, and how some of the parameters work.
    ASPSESSIONJJKKJJKK=LV2KJK44444444
    !--- The string prefix = ASPSESSION.
    !--- The string skip-length = 9. Skip
    !--- nine characters after the prefix.
    !--- The string process-length = 6, which would make
    !--- the string LV2KJK matching service server_g.
    ASPSESSIONSQPMMJHK=AARIKAMDESLD
    !--- Matches service server_h.
    Below is a sample configuration for the cookie strings.
    !************************** SERVICE **************************
    service server_g
    ip address 172.17.63.240
    string LV2KJK
    active
    service server_h
    ip address 172.17.63.241
    string AARIKA
    active
    !*************************** OWNER ***************************
    owner braden
    content server-cookie
    protocol tcp
    vip address 172.17.63.199
    port 80
    advanced-balance cookies
    string range 1 to 200
    string prefix "ASPSESSION"
    string skip-length 9
    string process-length 6
    add service server_g
    add service server_h
    active
    Kindly tell if this information is of any use to you.
    Sachin garg

Maybe you are looking for