Jdbc:oracle:thin:@ service name too long

I am going to use jdbc:oracle:thin:@ as my connection.
but my service name is too long....
is that any ways to include the long service name?
Thanks!

user652882,
Pardon me for asking, but how do you know your service name is too long?
Good Luck,
Avi.

Similar Messages

  • ATG CIM: Not able to connect to database jdbc:oracle:thin

    Hi All,
    I am trying to setup a ATG environment on windows boxes. Below is the setup:
    VM1) DC - Windows Domain Controller (Windows Server 2008)
    VM2) javadb - Oracle 11g (Windows Server 2008)
    VM3) javaweb - ATG 10.0.3 / WebLogic wlserver_10.3/ TomCat 7 (Windows Server 2008)
    Installation / Setup Progress
    * Oracle 11g installation successful. Sample DB successfully created.
    * WebLogic installation successful. Base_Domain successfully created.
    * Able to create successful connection to Oracle (javadb vm) from TomCat (javaweb vm) and query data
    Error: When configuring CIM I keep on getting >> "Not able to connect to database jdbc:oracle:thin:@javadb:1521:SampleDB @ scott"+_
    Corrective action already taken:
    1) Disabled firewall on all boxes
    2) Added path of JDBC driver (ojdbc6.jar) in Environment Variables
    3) Tested Oracle 11g (javadb vm) connectivity both from Eclipse and Tomcat. Which is successful
    4) Cleared all files under C:\ATG\ATG10.0.3\CIM\data to reset CIM
    Please refer CIM details below:
    ===========================================
    CIM DISPLAY START
    ===========================================
    -------ENTER CONNECTION DETAILS-----------------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    Production Core
    Select Database Type
    *[1] Oracle Thin
    [2] MS SQL
    [3] iNet MS SQL
    [4] DB2
    [5] My SQL
    Select one > 1
    Enter User Name [[system]] > scott
    Enter Password [[**********]] > **********
    Re-enter Password > **********
    Enter Host Name [[javadb]] > javadb
    Enter Port Number [[1521]] > 1521
    Enter Database Name [[sampledb]] > SampleDB
    Enter Database URL [[jdbc:oracle:thin:@javadb:1521:SampleDB]]
    >
    Enter Driver Path [[C:/Oracle/Middleware/wlserver_10.3/server/lib/ojdbc6.jar]]
    Enter JNDI Name [[ATGProductionDS]] >
    -------CONFIGURE DATASOURCE PRODUCTION CORE-----------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    [C] Connection Details - Done
    *[T] Test Connection
    [S] Create Schema
    Import Initial Data
    [D] Drop Schema
    [O] Configure Another Datasource
    > T
    -------TEST DATASOURCE CONNECTION---------------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    Production Core
    >> Not able to connect to database jdbc:oracle:thin:@javadb:1521:SampleDB @ scott
    ===========================================
    CIM DISPLAY END
    ===========================================
    ===========================================
    CIM LOG START
    ===========================================
    **** Warning     Mon Jul 23 22:46:25 IST 2012     1343063785645     atg.cim.worker.status.StatusUpdateValidator     Status id nonswitchingCore-DatasourceConnectionTemplateStep is unknown.
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator     Not able to connect to database jdbc:oracle:thin:@javadb:1521:SampleDB : -1     java.lang.ArrayIndexOutOfBoundsException: -1
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.T4CTTIoauthenticate.setSessionFields(T4CTTIoauthenticate.java:948)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.T4CTTIoauthenticate.<init>(T4CTTIoauthenticate.java:225)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:358)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:538)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:228)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at java.sql.DriverManager.getConnection(DriverManager.java:582)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at java.sql.DriverManager.getConnection(DriverManager.java:185)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.BasicDataSource.getDriverManagerConnection(BasicDataSource.java:526)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.BasicDataSource.getDriverManagerConnection(BasicDataSource.java:588)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.BasicDataSource.getConnection(BasicDataSource.java:475)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.FakeXADataSource.getXAConnection(FakeXADataSource.java:671)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.MonitoredDataSource.createResource(MonitoredDataSource.java:837)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.resourcepool.ResourcePool.populateSlot(ResourcePool.java:2064)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.resourcepool.ResourcePool.checkOut(ResourcePool.java:1332)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.MonitoredDataSource.co(MonitoredDataSource.java:1792)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.MonitoredDataSource.getConnection(MonitoredDataSource.java:1070)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.worker.databaseconfig.TestJdbcConnectionValidator.performTestConnection(TestJdbcConnectionValidator.java:319)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.worker.databaseconfig.TestJdbcConnectionValidator.validate(TestJdbcConnectionValidator.java:266)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.executeValidations(StepExecutor.java:280)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.ui.text.TextDisplay.processStep(TextDisplay.java:338)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.ui.UIDispatchImpl.processStep(UIDispatchImpl.java:89)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processStep(StepExecutor.java:201)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:80)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.runner.Runner.run(Runner.java:152)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:69)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:128)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:156)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processStep(StepExecutor.java:129)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:80)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.runner.Runner.run(Runner.java:152)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:69)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:128)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:156)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processStep(StepExecutor.java:129)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:80)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.runner.Runner.run(Runner.java:152)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:69)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:128)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:156)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processStep(StepExecutor.java:129)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:80)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.runner.Runner.run(Runner.java:152)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.types.LaunchWizard.execute(LaunchWizard.java:73)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:128)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:156)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processStep(StepExecutor.java:216)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:80)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.runner.Runner.run(Runner.java:152)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.flow.CimFlow.startupFlow(CimFlow.java:69)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.flow.CimFlowCreator.startDefaultCimFlow(CimFlowCreator.java:78)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.Launcher.startCimFlow(Launcher.java:168)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.Launcher.main(Launcher.java:68)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator     
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792218     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator     Error initializing connection from parameters. Test for jdbc connection failed
    ===========================================
    CIM LOG END
    ===========================================
    Any suggestion how to resolve this issue. Thanks in advance.
    cheers,
    Sandeep
    Edited by: 948180 on Jul 23, 2012 11:29 PM

    Hi,
    Earlier my ojdbc6.jar path was not at the beginning of ClassPath. I have made necessary changes. Please refer below:
    Environment Variables Settings on machine where CIM resides:
    PATH = C:\Oracle\Middleware\wlserver_10.3\server\lib\ojdbc6.jar+;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Java\jre7\bin;C:\Program Files\Apache Software Foundation\Tomcat 7.0\bin;C:\Program Files\cvsnt;C:\Program Files\Java\jdk1.7.0\bin;C:\Program Files\Sun\JavaDB\bin;C:\Program Files\Sun\JavaDB\lib;;C:\ATG\ATG10.0.3\MySQL\win32\bin;C:\ATG\ATG10.0.3\home\bin\;C:\Oracle\Middleware\wlserver_10.3\server\lib\;
    Note: I have verified by ojdbc6.jar path.
    Below are the precise steps I executed after updating my environment variables and restarting CMD.
    ===========================================
    CIM DISPLAY START
    ===========================================
    C:\ATG\ATG10.0.3\home\bin>cim.bat
    Nucleus running
    _ | () |
    __ _ | |_ __ _ ----
    / _` | | __| / _` |
    | (_| | | |_ | (_| |
    \__,_| \__| \__, |
    |___/
    Configuration Installation Manager
    =======CIM MAIN MENU============================================================
    enter [h]elp, [q]uit to exit
    Choose the task you want to perform:
    *[1] Database Configuration
    [2] Server Instance Configuration
    [3] Application Assembly & Deployment
    [P] Product Selection - Done (ATG B2C Commerce)
    [A] Select Application Server - Done (Weblogic Online)
    [C] Custom CIM Plugin Launcher
    > 1
    -------CALCULATE DATASOURCE DEPENDENCIES----------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    Calculating Datasource Dependencies. View log file at C:/ATG/ATG10.0.3/home/
    ../CIM/log/cim.log
    |. . |
    |. . |
    -------SELECT A DATASOURCE TO CONFIGURE-----------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    *[P] Publishing
    [C] Production Core
    [D] Done
    > c
    -------CONFIGURE DATASOURCE PRODUCTION CORE-------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    [C] Connection Details - Done
    *[T] Test Connection
    [S] Create Schema
    Import Initial Data
    [D] Drop Schema
    [O] Configure Another Datasource
    > t
    -------TEST DATASOURCE CONNECTION-----------------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    Production Core
    >> Not able to connect to database jdbc:oracle:thin:@javadb:1521:SampleDB @
    scott
    *[E] Edit Connection Details
    [R] Redo
    [D] Done
    > e
    -------RE-USE VALUES FROM PREVIOUS DATASOURCE-----------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    Production Core
    Base on previous database details:
    [1] system@jdbc:oracle:thin:@javadb:1521:sampledb
    [2] scott@jdbc:oracle:thin:@javadb:1521:SampleDB
    *[3] None/Use Existing
    Select one > 2
    -------ENTER CONNECTION DETAILS-------------------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    Production Core
    Select Database Type
    *[1] Oracle Thin
    [2] MS SQL
    [3] iNet MS SQL
    [4] DB2
    [5] My SQL
    Select one > 1
    Enter User Name [[scott]] > scott
    Enter Password [[**********]] > **********
    Re-enter Password > **********
    Enter Host Name [[javadb]] > javadb
    Enter Port Number [[1521]] > 1521
    Enter Database Name [[SampleDB]] > SampleDB
    Enter Database URL [[jdbc:oracle:thin:@javadb:1521:SampleDB]]
    > jdbc:oracle:thin:@javadb:1521:SampleDB
    Enter Driver Path [[C:/Oracle/Middleware/wlserver_10.3/server/lib/ojdbc6.jar]
    ] > C:\Oracle\Middleware\wlserver_10.3\server\lib\ojdbc6.jar
    Enter JNDI Name [[ATGProductionDS]] > ATGProductionDS
    -------CONFIGURE DATASOURCE PRODUCTION CORE-------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    [C] Connection Details - Done
    *[T] Test Connection
    [S] Create Schema
    [I] Import Initial Data
    [D] Drop Schema
    [O] Configure Another Datasource
    > T
    -------TEST DATASOURCE CONNECTION-----------------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    Production Core
    >> Not able to connect to database jdbc:oracle:thin:@javadb:1521:SampleDB @
    scott
    *[E] Edit Connection Details
    [R] Redo
    [D] Done
    >
    ===========================================
    CIM DISPLAY END
    ===========================================
    Don't understand what could possibly be going wrong.
    Cheers,
    Sandeep
    Edited by: 948180 on Jul 24, 2012 12:23 AM

  • Service username too long???

    Hi gurus,
    I'm installing NW2004s on Oracle 10.2 (patched to 10.2.0.2) and Windows 2003. During install I got following error:
    ORA-20000: Service username too long: max length is 30
    ORA-06512: at line 23
    It seems that actually my O$<domain>\sapservice<sid> username has 31 characters (long domainname). What can I do? I can't change domain name and my installation is stuck
    Regs,
    FS
    PS. Points will be rewarded!!!

    Fortunatelly it was just 1 char and setting os_authent_prefix='' solved my problem.
    Thx!!!
    FS

  • File name too long cannot copy (cont'd)

    This is a continuation of the post started September 01, 2009, with the last post on
    October 17, 2011 named File name too long cannot copy
    Since this is an ongoing unsolved issue, and the thread was locked, it continues here.
    It is ever so easy to create a long file/path using explorer.exe as will be shown below.
    What needs to be solved is, what is an easy way (no, not by listing out all the files in a directory to a text file and counting characters), perhaps using a shell extension, to find out which files in a directory and it's subdirectories will be (or were)
    too long to copy, (and then perhaps even copying those over either intact or renamed)?
    Maflagulator said:
    I'm running the 7100 build...enjoying it except for one big thing:
    While attempting to copy 402gb from my main storage volume onto a spare 500gb drive (for the purpose of changing to a new RAID array) I've come across something that I would expect a Windows 98 OS to give me.
    It tells me that a file has TOO LONG of a file name, then provides with two unhelpful options: SKIP or CANCEL
    I never had XP give me an issue like this at all, so what gives? And while some specific files did have long file names (such as for songs, etc.) it had 7 issues with folders stating that their name was too long, but in fact they were not since they were
    titled '07-06-07' for the date that I dumped the audio files in them. However, they may have contained FILES with long file names though.
    Anyone else get this same situation? Perhaps the RTM version does not do this? Can anyone verify this regarding their install of the RC or the RTM?
    It made it through 400gb out of the 402gb transfer.
    I'm just happy to see that it doesn't spazz out about an issue like this until it has done all the other transfers that it can do because it saves the issues it has with files until the very end. In XP it would spazz about it the moment it came across it
    causing the transfer process to halt.
    Since long path/file names can so easily be created on Win7, it might be useful to see a typical way this happens, which might then give clues how to work with them.
    In Windows Vista, we learnt from:
    File names and file name extensions: frequently asked questions that:
    Windows usually limits file names to 260 characters. But the file name must actually be shorter than that, since the complete path (such as C:\Program Files\filename.txt) is included in this character count.
    In Windows 7, we are told here:
    File names and file name extensions: frequently asked questions that:
    It depends on the length of the complete path to the file (such as C:\Program Files\filename.txt). Windows limits a single path to 260 characters. This is why you might occasionally get an error when copying a file with a very long file name to a location
    that has a longer path than the file's original location.
    From the Windows Dev Center - Desktop, we read about Maximum Path Length Limitation here:
    Naming Files, Paths, and Namespaces
    This helps us understand why a folder can be a maximum of 244 characters, from the defined 260 length of MAX_PATH as follows:
    260 minus C:\ (3) minus <NUL> (1) = 256
    256 minus 8.3 file name (12) = 244
    We also learn there that: The Windows API has many functions that also have Unicode versions to permit an extended-length path for a maximum total path length of 32,767 characters.
    And we read the claim that: The shell and the file system have different requirements. It is possible to create a path with the Windows API that the shell user interface is not be able to interpret properly.
    There is also a comment below this document that reads: In a previous iteration of this document, it is mentioned that The Unicode versions of several functions permit a maximum path length of approximately 32,000 characters composed of components up to
    255 characters in length. This information is now gone.
    So we are in a position where the file system and Windows API can create long path/flies that the shell cannot handle.
    But then we need to be able to handle it, so a little exploration might lead to a better understanding of how to do this.
    For most tasks being performed on long folder/files, Windows 7 and other Windows programs balk when the Path+Filename length > 260
    Let's create a long path/file.
    Create a folder called A at the root of a Drive.
    Create a sub-folder of A called: B
    Create a sub-folder of B called: C
    Make a FILE in sub-folder C called (no spaces or break, one long continuous string): 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T
    123456789U123456789V123456789W123456789X123456.txt
    Rename sub-folder C to the string (no spaces or break, one long continuous string) (The actual directory created will be slightly shorter than this full length): 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J
    123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X123456789Y123456789Z
    Rename sub-folder B to the same full string above. (The actual directory created will be slightly shorter than this full length but 2 characters longer than the step above.)
    Rename folder A to that same full original string. (Again the actual directory created will be slightly shorter than this full length but 2 characters longer than the step above.)
    You now have the lovely file placed at (the breaks are just so it fits into the screen):
    C:\123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X1234\ 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J
    123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X12\ 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T
    123456789U123456789V123456789W123456789X\ 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X123456.txt
    You have a folder length of over 700 and a file length of over 250 for a total of over 950
    However you will notice that each folder, when created, could only be a maximum of 247 charachters including the path (example C:\ , & C:\A , & C:\A\B
    This only applies backwards, that is up the path. It did not matter what was further down the path.
    Now, you can't easily access or rename the file, but you can rename the folders easily.
    For best results, start renaming from the top of the Tree, working down the subfolders, because renaming from down up will limit you, and in fact won't work if the folder lengths are too long.
    So how might knowing this help us?
    Well, to copy this long_file from the C:\ drive to the D:\ drive, and keeping the path structure, this should work:
    Note the name of the top folder. Rename it to something very short, say: A (Make sure C:\A does not exist)
    Note the name of the 2nd folder. Rename it to something very short, say: B (Make sure C:\A\B does not exist)
    Note the name of the 3rd folder. Rename it to something very short, say: C (Make sure C:\A\B\C does not exist)
    Make sure D:\A does not exist - then copy the A folder on disk C: to disk D: (which gives you D:\A\B\C\long_file
    Rename D:\A\B\C to D:\A\B\Original_3rd_Folder_name
    Rename D:\A\B to D:\A\B\Original_2nd_Folder_name
    Rename D:\A to D:\Original_top_Folder_name
    Rename C:\A\B\C back to their original names, in this same reverse order starting with C, then B, then A
    Note: If using Explorer, at some points you might have to press the F5 refresh key.
    This is of course how you might copy such long path/files without using the other more "easy" techniques for the "normal" everyday user like:
    sharing a sub-folder
    using the commandline to assign a drive letter by means of SUBST
    using AddConnectionunder VB to assign a drive letter to a path
    using the "\\?\" prefix to a path string to tell the Windows APIs to disable all string parsing and to send the string that follows it straight to the file system
    and so on.
    See how simple Windows can be for Dummies!
    But then, how can we know that files to be copied exceed this MAX_PATH? Or also after a copy has taken place, know exactly which files that have NOT been copied because of exceeding the MAX_PATH limit, and then a procedure to copy these either by renaming
    them, or by copying them intact as they are?
    There have been suggestions to use
    LongPathTool, but this does not have a facility to check a series of folders and tell you which files are going to be caught by the error when copying. So once a copy has taken place using Windows 7, one does not know which files did not get copied, and
    where exactly they are located.
    Neither does the free
    Old Path Scanner do that. It can only check for overly long directory paths, but misses out when the directory path is within limits, but adding in the file name puts it out of bounds.
    So, as shown above, it is ever so easy to create a long file/path using explorer.exe
    So, what then is an easy way (no, not by listing out all the files in a directory to a text file and counting characters), perhaps using a shell extension, to find out which files in a directory and it's subdirectories will be (or were) too long to copy,
    (and then perhaps even copying those over either intact or renamed)?

    This is a not a "solution" ....but a "work around": a low tech fix....for error message "your file name is too long to be copied, deleted, renamed, moved" :
    1.   problem is this: the "file name" has a limit on number of characters.....the sum of characters really includes the entire path name; you gotta shorten it first (i.e, if the total number of characters in the file name + Path name are over the
    limit, the error appears).  The deeper your file folder sub levels are, the more this problem will come up, especially when you copy to a subfolder of a subfolder/subfolder of another path ...adds to character limit)
    2.  How do you know which combined file names + path names are too long if  you are in the  middle of a copy operation and this error pops up?  Some files copied but the "long files error message" says "skip" or "cancel" ... but not which
    files are the "too long" ones.  If you hit "skip" or "cancel" the "too long" files are left behind...but are mixed in with non-offender "good" "short name" files.   Sorting thru 1000s of "good" files to find a few "bad" ones manually is impractical.
    3.   Here's how you sort out the "bad" from the "good":
    4.    Let's say you want to copy a folder ..."Football" ...that has five layers of subfolders; each subfolder contains numerous files:
      C:/1 Football / 2 teams/ 3 players/ 4 stats/ 5 injuriessidelineplayerstoolong 
           There are five levels root "1 football" with subfolders  2, 3, 4 and lastly "5 injuries"
    5.    Use "cut" and "paste"  (for example to backup all five levels to a new backup folder):
           select "1 football" ....cut....select target folder....paste 
           ("cut" command means as the files are copied to the target destination, the file is deleted from the source location)
          Hint: avoid "cut" and "paste" to a target folder that is itself a sub/sub/sub folder ...that compounds the "characters over the limit" problem ...because the characters in the sub/sub/sub folder are included in the "file name
    character limit"...instead "paste" to a C:/ root directory.
           Suppose in the middle of this operation...error pops up: "5 files have file names that are too long"  Skip or cancel?
           select "skip"  ...and let operation finish
    6.    Now go back and look at the source location: since the software allows only the "good" "short name" files to be copied (and because you "skipped" the "bad" "Long name" files so they are not copied or deleted) ...all that remains
    in the source location are the "bad" "long name files" (because "good" ones were deleted from the source location after the "cut" operation...the bad ones stick out like a sore thumb.
    7.   You will find ....all that remains in source folders are: the "bad" "too long" files; in this example the "bad" file is in level 5:
          C:/ 1 football / 2 teams /3 players /4 stats /5 injuriessidelineplayerstoolong
    8.   select folder 5 injuriessidelineplayerstoolong (that's right...select folder, not file) gotta rename the folder first.
    9.  hit F2 rename folder..folder name highlighted...delete some of the letters in the folder name:
           like this:   5 injuriessidelineplayers  ....you should delete 'toolong'....from the folder name
    10.  then go into folder 5....and do the same operation ...with the too long file name:
            hit F2 rename file....file name hightlighted...delete some of the letters
               like this:  injuriessidelineplayers.....you should delete 'toolong' from the file name
    11.  Now..."cut and paste"  the renamed file to the target backup folder.  
    The Error message will pop up again if you missed any "bad" files....for example, it will indicate "5 files too long" ....then repeat process 5 times until you fix all of them
    12.     Finally, copy the target destination files back to the source location (when you are certain all source location file folder locations are empty) 
    Of course, this "makeshift" solution would not be necessary if MSFT would fix the problem...

  • File communication channel issue : object name too long

    Hi Experts,
    My requirement is to place the successful files in folder and un-successful files in one folder after processing.
    we used parameterized mapping to achieve this requirement.
    I'm facing below issues, please help me to resolve.
    " An error occurred while connecting to the FTP server. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 501 Unexpected reply codeSpecified object name too long, limit is 10 characters: $Filepath_Su.'. For details, contact your FTP server vendor.
    As per my understanding it is not taking the path specified,because of length issue.
    Please send me your valuable inputs and help me.
    Thanks in advance for your help.
    Regards
    Bhargava Krishna

    Hello,
    By loking ur error description, it's quite evident that it's a FTP sever issue?
    Sometime on FTP server, there is a check which is enabled to limit the length of file names, and i think the same has been recently implemented on ur FTP server. So instead of changing ur config, check with ur FTP admin.
    Tested the same after tweaking existing FTP server settings.
    Thanks
    Amit Srivastava

  • Jdbc:oracle:thin:@[host]:[port]:[sid] problem:

    Hi all
    When I try to make connection through this string jdbc:oracle:thin:@localhost:1521:orcl , It failed to connect to the database.
    I am trying to connect to database through obiee 11.1.1.5 by jdbc connectivity.
    Please tell me its solution.....
    Thanks
    Rizwan Ali

    Hi,
    The TNSNAME.ora that the OBIEE11g uses is insede the folder <OBIEE11g_HOME>\Middleware_Home\Oracle_BI1\network\admin
    (DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = IP address)(PORT = 1521))(CONNECT_DATA =(SERVER = DEDICATED)(SERVICE_NAME = orcl)))
    Refer
    http://123obi.com/2011/03/error-the-connection-has-failed-in-obiee-11g/
    http://gerardnico.com/wiki/database/oracle/connect_descriptor
    FYI: OTN Message:
    1. If you just need one TNS alias, then copy the database connection descriptor from database tnsnames.ora file to the tnsnames.ora file under the BIEE directory:
    [middleware home]/[oracle home]/Oracle_BI1/network/admin
    2. You may also copy the entire tnsnames.ora file
    3. Another alternative is to set the TNS_ADMIN environment varaible which would point to the directory where a tnsnames.ora file is located. This would need to be set as a System Environment variable in Windows or in the command shell if starting from a command-line. For Unix/Linux, it would need to configured in the user profile that owns the software or set explicitly in the shell if starting from the command-line. See Note 111942.1 Setting TNS_ADMIN Environment Variable for more information on adding this environment variable.
    Thanks
    Deva

  • Connection reset using JDBC Oracle thin Driver (towards 10g DB)

    Hi we have a home-grown application and a Oracle 10g (10.2.0.1) database.
    We created a scheduled servlet that gets a JDBC connection from a persistent connected cache (an OracleDataSource object registered using OracleConnectionCacheManager). The servlet runs every 15 minutes and runs the query "SELECT SYSTIME FROM DUAL" on 10g Database as XYZ user. The datapool was created yday on web-app and all queries ran successfully for about 5 hours after which it reported a connection reset error.
    I can then conclude that we cannot keep the server session alive for the JDBC client by running frequent SQL queries.
    We didnt get any messages on the DB server side that indicate the release of the session
    Ultimately, we are struggling with reset connections from our applications that are
    using the JDBC thin oracle driver; after a couple of hours of idle
    connections, we receive the below error from the JDBC driver:
    Jul 5, 2007 10:59:53 AM oracle.jdbc.driver.DatabaseError throwSqlException
    WARNING: DatabaseError.throwSqlException(e): Unable to find ORA number from
    exception Jul 5, 2007 10:59:53 AM oracle.jdbc.driver.DatabaseError
    findMessage
    WARNING: DatabaseError.findMessage(errNum, obj): returned Io exception:
    Connection reset Jul 5, 2007 10:59:53 AM
    oracle.jdbc.driver.PhysicalConnection getWarnings
    INFO: PhysicalConnection.getWarnings()
    Any suggestions please ?
    Vk

    The code itself is fine; the problem is with one of:
    1) the connection URL
    2) intermediate networking
    3) the database itself
    1) your connection URL is "jdbc:oracle:thin:@127.0.0.1:1521:orcl"
    - is Oracle really running on the default port, 1521
    - is the installation SID really "orcl"
    2) lots of possibilities, but only a couple are likely
    - is TCP/IP configured and running on your host
    - is there a persoanl firewall rpduct running? perhaps it's blocking the connection
    3) Is Oracle running?
    Is the listener running?

  • Disk Utility (10.5.6) error: File name too long

    Hello, here is one for you all...
    I am in the midst of creating a new "build image" so I can start deploying Leopard.
    Before I upgraded the build to 10.5.6 I was able to create a disk image of this build machine.
    After updating it to 10.5.6 and all of the current Apple updates I am no long able to create a disk image.
    I keep getting an error several minutes into the imaging process that says +"*File name too long".*+
    I've run permission repair on the disk and Disk Warrior with still no luck. I've also used different machines and a boot FireWire drive to make he image and still have had no luck. I can use CCC to clone my Master build to another machine but I need to be able to make an image of it.
    Thanks in advance for any help.

    Bear in mind that in Unix, a file name includes the path, so if you have a very deep file or perhaps some kind of infinite recursive link, that might cause the problem, since that would make the file name very long indeed.
    This may not be the problem you are having, but it just came to my mind when I read your post

  • "Maximum number of application files exceeded or file names too long"...help!!!

    Hi there…
    I am trying to create a game for my mobile.
    The “problem” is that I have more than 500 swfs that I want to pack using the Adobe Mobile Packager. And I am getting this error:
    “Maximum number of application files exceeded or file names too long”
    How could I solve this problem?
    Thanks everyone!
    Cheers.
    Leo.

    500??  What are there so many files?
    The problem is that the CAB format only allows for 300 files maximum, so there's nothing that we can do about that I'm afraid.
    Mark
    www.flashmobileblog.com

  • JAXB: Error compiling classes generated by xjc (file name too long)

    Hi friends,
    I am trying to compile classes that are generated by using XJC tool on xsd file. The compilation fails with following message.
    buildxsdmodel:
        [javac] Compiling 794 source files to /home/uchamad/working/teleworker/ejb/build/classes
        [javac] /home/uchamad/working/teleworker/ejb/build/tmpsrc/uk/co/novatel/teleworker/model/wlr/bulksearch
    results/impl/ApplicationInformationTypeImpl.java:58372: error while writing
    uk.co.novatel.teleworker.model.wlr.bulksearchresults.impl.ApplicationInformationTypeImpl.XMLRequestID
    TypeImpl.SearchOrderResultsTypeImpl.SearchTypeDetailTypeImpl.OrderTypeImpl.OrderDetailsTypeImpl.
    OrderLinesTypeImpl.NumberPortingTypeImpl.OLODetailsTypeImpl.NumberLocationTypeImpl.OLOMainP
    STN1AddressTypeImpl.Unmarshaller: /home/uchamad/working/teleworker/ejb/build/classes/uk/co/novatel
    /teleworker/model/wlr/bulksearchresults/impl/ApplicationInformationTypeImpl$XMLRequestIDTypeImpl$S
    earchOrderResultsTypeImpl$SearchTypeDetailTypeImpl$OrderTypeImpl$OrderDetailsTypeImpl$OrderLin
    esTypeImpl$NumberPortingTypeImpl$OLODetailsTypeImpl$NumberLocationTypeImpl$OLOMainPSTN1A
    ddressTypeImpl$Unmarshaller.class (File name too long)
        [javac]                                             public class Unmarshaller
        [javac]                                                    ^
        [javac] 1 error
    The compiler is complaining about the file name being too long. This is happening because the java classes when generated from XSD contains deep nesting of inner classes. So when it comes to compile the .class name file is too long for the operating system.
    I am trying this on unix box.
    I wonder if there is a way to configure XJC so that it does not produce inner classes but instead keep them out.
    Any help would be appreciated.
    many thanks
    Usmangani

    Flattening your schema definition will flatten the output files, too -- that will probably be nice for coding as well since you wont have to use class names such as SomeTypeNestedInAnotherTypeThatHasYetAnotherType. Instead of having all of the elements defined directly within the enclosing root element, define logical chunks at the top level and incorporate them in the definition of real root element of your documents by reference.

  • Permission required to access oracle client service names

    Hello,
    I  actually have a problem with accessing oracle client service names in Crystal.
    The problem is:
    I installed crystal reports 2008 and installed oracle client on a machine (I used an account that is a local administrator of the machine during installation) but the problem is that the users who are going to access crystal are standard users and they couldnu2019t access the services in oracle client and when they try to refresh the report they get the following error
    "Failed to load database information. Details: the DB connector 'crdb_oracle.dll' couldn't be loaded. the correct version of the database client for this database type might not be installed"
    I gave the users permission on the two folders (C:\program files \Common files \) and RegEdit : (C:\Windows \ System 32\) but the problem wasnu2019t solved so I made them local administrators and the problem was solved but I donu2019t want to make the users  local administrators on the machine , some people told me that I have to install oracle client with the user who will be using crystal but the problem is that two users will be working on the machine not just one and they have two different accounts and when I tried to give the users full control permission on oracle folder , the problem wasnu2019t solved, So I wanted to know if any one faced a similar problem and how to solve it without making the users local administrators.
    Thanks in advance.

    Hello,
    It appears you have everything installed and configured for Cr to work so it looks like it's a DB issue.
    What do you see in the logs if you enable logging on the Server? Are your requests even getting to the Server from CR under the user account?
    Test it using the admin and then the user account.
    You could try checking on the option to use Trusted Authentication in the database log on windows of CR. This should pass the users PC log on credentials to the Server.
    Thank you
    Don

  • Column Name too long

    While loading the data from XML source I am getting following error
    ORA-00972: identifier is too long
    I understand that some of the Column name are more then 30 char (Oracle Limit) inmy source but I like to know what needs
    to be modified in the IKM to pick only first thirty characters of column name in case of column name is more then 30 Char.
    The LKM works fine as it take only the first 30 char to create the table name, I think it take that setting from topology manger.
    but what need to modify in IKM to take only first 30 char for column name.
    I am creating target table on the fly and I dont wanna modify each column name in the target table, It'll be alot of work for me.
    Please let me know your thoughts on this.
    Thanks

    Yes its erroring out for IKM step for creating target table.
    The step is ignoring the error on Create Target Table because of following error
    972 : 42000 : java.sql.SQLException: ORA-00972: identifier is too long
    java.sql.SQLException: ORA-00972: identifier is too long
    ofcourse the column name is longer then Oracle limitation that is 30 Chars.
    In the next step for inserting data it is also failing because of same error.
    LKM steps work fine as it strip the column name longer then 30 char.

  • Consolidating Library Error: File Name Too Long, But What File?

    I am trying to consolidate my library to put all my music (very unorganized) in one spot so I can back it all up. When I try to consolidate, it takes a second to prepare, then immediately brings up an error window saying "Copying Music Failed. The file name was invalid or too long."
    How do I fix this? I really would like to back up my music!

    Hi, ZeroGravity107.
    This can be a tricky problem to figure out since iTunes doesn't specify what file name is "invalid or too long" and there's no documentation on what determines if a file name is "invalid or too long".
    We had one user report that he was able to use his/her keen eyesight to note the last file that appeared before the error message appeared and it turned out that file was the cause of his/her trouble.
    If your eyesight isn't that keen, I'd suggest concentrating on the file name being too long possibility.
    The entire directory path leading to the file is considered part of the file name so, as an example, iTunes' default settings might place a particular file at C:\Documents and Settings\ user name \My Documents\My Music\iTunes\iTunes Music\artist folder\album folder\whatever.m4a.
    Is the directory path leading to your consolidated location much longer than that?
    polydorus has suggested a way to look over your file names: Assuming your music is currently in the default location, make your way there with Windows Explorer and select List in the View menu menu and see if anything stands out as being unusual.

  • Can't access files with names too long

    I have some files on a Windows formatted external hard drive that have filenames that seem to be too long for OS X to handle. I can't open them, nor can I delete them. I can't even seem to "rm" them from the command line. I know they're there, and not just some bitwise mirage. Does anyone have any way to deal with these files (they're 0 bytes long, as far as the Finder is concerned, and if you click on them, they disappear)?

    MacOS X supports file names of 256 characters (or is it 255?). Are your files names longer then that? If not, then I would suspect the problem is somewhere else, probably permissions.
    When you try to rm the file, does it produce an error? If so, what is it?

  • Receiving ERROR meassage when trying to copy..file name too long.

    Hello.
    There is an error code number, but didn't write it down...will do so, if no-one can answer this question at the minute. I am not at the Mac at the moment, so this post is pre-emptive.
    Problem:
    If I try to copy over a folder with photoshop images onto another drive, the copy is incomplete due to the name/s of the files being too long, apparently.
    The error message says something to the effect: 'the names are too long can't complete copy'.
    The file names are about 10-12 [at most]characters in length.
    Please advise
    Chris

    If the drive is formatted HFS then you are limited to 32 characters on a file name. If it is formatted HFS + then you can have file names as long as 255 characters. I am not familiar withi the format you say the drive is formatted in so I can't speak to it.
    If you are receiving -50 errors that can indicate a file name that is too long OR an illegal character in the filename regardless of its length.
    If you are actually using 10.3.8 as your profile states then that may be part of the problem. Many of these problems existed in 10.3.X but were fixed in 10.4
    I remember that 10.3.8 had issues copying to external drives when there were more than a certain number of characters in a filename. I don't remember the number but for some reason 10 or 12 is what comes to mind. It caused me many problems when I would try and copy files to a Zip disk that I used to have. Since I updated to 10.4 those issues have never occured again.
    Since you know what folder the problematic files are in why not just open the folder and try to copy files one at a time. When you get to the one(s) that is a problem, change the file name to something shorter.
    A better solution would be to update to 10.4 but with 10.5 coming out sometime in the Spring of 2007 this may not be the time.

Maybe you are looking for