ACS User Database Export

Is it possible to export the user database stored in the Cisco Secure ACS Database to some file. I need to see all the user accounts and their group assignments etc to be able to do reporting on this.
Any ideas?

yes... csutil -d will dump the db.
look at aaa-reports (www.extraxi.com) they can import the dump file and run reports off it.

Similar Messages

  • ACS User database Backup

    Is it possible to have the ACS user database in an excel sheet

    Hi,
    You can open .dmp file in notepad but that will not provide any info as its not user readable.
    You need to export the lsit of users in .txt extension
    here is the command that you need to run from the command prompt where ACS is installed
    start > run> cmd > go to this dir
    C:\Program Files\CiscoSecure ACS v4.2\bin>net stop csauth
    CSUtil.exe -u user.txt
    C:\Program Files\CiscoSecure ACS v4.2\bin>net start csauth
    Then you can easily access user.txt file in notepad.
    HTH
    JK

  • ACS User database problem

    I have installed an ACS 3.3 on win 2003 server and I've encountered this problem:
    Durin a mudification of some user (group belongings)some of this users, have been duplicated and une of this assigned to default group.
    At this time these users (default group)is not possible to delete it.
    Can anyone help me?
    Tranks and Regards

    This appendix contains details on the Cisco Secure ACS command-line utility, CSUtil.exe. You can use CSUtil to import username, password, and group information all at once from a standard text file to back up and maintain your database.
    http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/csacs4nt/csnt26/usergd26/apimport.htm

  • Acs user database

    Can I limit the number that can use a specific user entry to 1 at a time in acs

    I wouldnt say it cant be done... but you have to look and make sure the NAS-Port attribute looked sensible. Going back a few years I know Aironet, for example, was quite tricky to make work with max sessions.
    The other thing is that because wifi comes and goes its hard for the AP to know when the session has finished. Max sessions was implemented with Dial in mind (yes thats how old it is!!!) ie real physical ports.
    With wifi you could look at the number of mac ids in user by a user at any one time as a way to control concurrent sessions.
    No not impossible, but probably unlikely to work reliably.

  • How to manipulate the large Cisco ACS user database?

    e.g. I have to change the settings of "disable the account if failed attempts exceed times" one by one. Is there a batch method of operation?

    Use the JDBC-ODBC driver which is already installed with the JDK.
    The best place to look is the Java Tutorial on JDBC which will gve you the basics, check out
    http://java.sun.com/docs/books/tutorial/jdbc/basics/index.html
    This will show you how to get a connection and from there it should be a matter of using standard SQL calls

  • Export User-Database between ACS-Server

    Hi everyone ,
    an ACS 2.3 is running under Unix with 3000 based user. The job is, to migrate the user-database to a new ACS-Server under Windows.
    On the unix-version 2.3 there is no way to export the database to external.
    The only way, i hope, is to mirror the old and the new server as redundant server and if the database is mirrored on both server, than the database is ready for export.
    Is this correct?
    Is there an other way?
    Thanks for your input.
    Ralf

    The migration should go to version 3.1 or 3.2 .
    Ralf

  • ACS 4.2.1.15 External User Database 'Authen DLL '

    Having CSACSE-1113-K9 with ACS 4.2.15.
    I want to confiure windows user database under extrenal user database but i get an error  (attached) 'An error has occured while processing the Authen DLL Configure pagebecasue an error occured....'
    External User Database----->database configuration --->Windows Database------>Configure.
    I tried to stop the services and start agian but the same issue.
    Th eappliance is secondary (backup) ACS. On the primary it is working fine.
    Any help would be appreciated.
    Regards,
    BJ

    Hi Abdul,
      Can you check if the remote agent on the windows server box is running the same 4.2.1.15 version as well.
    Like if  ACS -4.2.1.15   then make sure that remote agent is also 4.2.1.15
    or
    if ACS is running 4.2.1.15 patch 2 then remote agent should also be 4.2.1.15 patch 2
    Let me know if the version is same and if not then install the remote agent correctly and try again.

  • ACS and Windows 2000 user database communication port

    Could my Windows 2000 SP4 + ACS v3.23 can install any new Windows 2000 service pack ?
    I'm affraid to infect ACS Service.
    So, I want to install firewall on this server to block malicious traffic.
    However, my ACS used external user database Windows 2000 for authentication.
    Who can tell me What protocols or port list they are communication?
    I have to avoid these traffic on my firewall.

    Hi cheng
    I think you can install any servie pack without problem and the SP4 is the latest one for WIN2000 and you server already has this SP
    For your second question you need to specify many protocols according to your active directory config in this link you can find a list of this protocols and the best way is to make debug or logging or use a siniffer to know the exactly protocols flow between your ACS and AD server
    http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/activedirectory/deploy/confeat/adrepfir.mspx
    Best Regards

  • ACS support Kerberos User Database?

    Hi,
    I've a customer currently having kerberos user database. I proposed to him to implement ACS to enable 802.1x on wireless client. Can ACS support or integrate with Kerberos User Database? If yes, any user guide which list out the steps on doing so?
    I searched through Cisco website but failed to find any info related to the integration of ACS with Kerberos User Database.
    Thank.
    Delon

    For network users who are authenticated by a Windows user database, Cisco Secure ACS supports user-changeable passwords upon password expiration. You can enable this feature in the MS-CHAP Settings and Windows EAP Settings tables on the Windows User Database Configuration page in the External User Databases section.

  • Export UB10 user database

    I thought both MS and UB databases were combined, but when I brought by user database in my merge database, the UB footprints didn't follow.
    I've gone through the great pains of rebuilding my UB database and I want to properly export it like MS does. How is this done??????????
    Why isn't there an export option? Anyone?Message Edited by kittmaster on 07-20-2007 11:29 AM
    Signature: Looking for a footprint, component, model? Might be here > http://ni.kittmaster.com

    At this point all of my databases are rebuilt in ver 10 as the were in version 9.
    So, example. I've created the LM3914 with its spice model in MS10, it also has a footprint that is linked to UB.
    Now, if I export the MS database as a prz file, the UB footprint data.....is it there?
    In version 9 when this setup was exactly as described above for version 10, when I exported the V9 database, it only save the MS data!!
    I know this because when I tried to import my V9 database into V10, its said invalid format. And of course there is NOTHING in the help file to tell you how to handle this error.....basically if your screwed if you have no intitive to comb through forum (which is how I found my partial solution) to use the "convert database" function which then took the V9 database and converted it to V10. The only data that was imported was the MS data/spice info. The UB9 footprint data never came in.
    I had to MANUALLY rebuild every single part from the ground up because there seems to be no way to export UB footprints in the fashion that MS9/10 does for its parts.
    I understand that they are "partition" but it seems the focus is directly on MS functionality and little on the UB but yet they are supposed to be "interlinked". That doesn't seem to be the case here.
    I have not tried to export version 10 databases and try to reimport them because I don't want to have to go through the headache of starting from ground zero..............again
    If you need more help, you can contact me via my email and I can give you a direct line to help clarify or to speed this issue up.
    Thanks
    Chris
    Signature: Looking for a footprint, component, model? Might be here > http://ni.kittmaster.com

  • Intergrating ACS with user database in windows DC

    Please,
    I just installed and configured ACS on window 2003 server on my network. The next task is to integrate the user database in my DC with the ACS. I need you to tell me in steps what else that need to be done.The documentaion is not specific.
    (I heard about 'remote agent' please what is this,and is it required?)

    I think you can map your DC groups to ACS group
    http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_server_for_windows/4.0/user/guide/qg.html#wp940538
    M.

  • Multisim: export user database grayed out

    Hello,
    I want to export the user database but I can't because this option is grayed out.
    Multisim 12
    Windows 7
    Any idea why?
    Any suggestions and/or ideas?
    TIA
    Stefaan Claes
    Solved!
    Go to Solution.

    Hi Stefaan,
    You can follow this guide to get your databases exported. You probably using full base or education version of Mutlisim and need to do a manual copy as described below.
    http://digital.ni.com/public.nsf/allkb/C61ADD277A26C12786257D8C006F4E01?OpenDocument
    Best Regards
    Jonas Mäki
    Applications Engineering
    National Instruments

  • Database export stops with the following warnings.

    Hello,
    I am doing a Database Export/Import Activity. My DB is MS SQL server 2000 and SAP R/3 (4.6C SR2 , 4.6D kernel).
    When i try to do a DB export with option split STR and EXT files, my export stops abruptly without giving any erorrs but with a whole list of warnings.
    My splitting procedure is using SPLITSTR.PL perl script. I am not using the latest java based split.
    For your reference i am pasting the whole DBEXPORT.log file.
    (sorry its bit large,,, i hope you dont mind ) )
    INFO 2008-03-29 14:36:21 CommandFileController SyFileVersionSave:736
        Saving original content of file
        C:\Users\prdadm\Install\DBEXPORT.R3S ...
    INFO 2008-03-29 14:36:21 CommandFileController SyFileCopy:676
        Copying source file C:\Users\prdadm\Install\DBEXPORT.R3S to
        target file C:\Users\prdadm\Install\DBEXPORT.R3S.1 ...
    INFO 2008-03-29 14:36:21 CommandFileController SyPermissionSet:2207
        Changing permission for file C:\Users\prdadm\Install\DBEXPORT.R3S
        from 777 to 666.
    INFO 2008-03-29 14:36:21 Main
        Preparation successfully completed.
    INFO 2008-03-29 14:36:23 DBEXPORTINSTANCE_NT_IND DefValForKey_OS:0
        R3Setup found the share 'SAPLOC' on drive E:.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
        checking host name lookup for 'ELESAPTMP1'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
        offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
        host 'ELESAPTMP1' has ip address '172.18.101.21'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
        offical host name for '172.18.101.21' is 'ELESAPTMP1'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
        checking host name lookup for 'ELESAPTMP1'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
        offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
        host 'ELESAPTMP1' has ip address '172.18.101.21'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
        offical host name for '172.18.101.21' is 'ELESAPTMP1'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
        checking host name lookup for 'ELESAPTMP1'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
        offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
        host 'ELESAPTMP1' has ip address '172.18.101.21'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
        offical host name for '172.18.101.21' is 'ELESAPTMP1'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:434
        checking host name lookup for 'ELESAPTMP1'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:473
        offical host name for 'ELESAPTMP1' is 'ELESAPTMP1.lntebg.com'.
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:541
        host 'ELESAPTMP1' has ip address '172.18.101.21'
    INFO 2008-03-29 14:36:37 DBEXPORTINSTANCE_NT_IND SyCheckHostnameLookup:581
        offical host name for '172.18.101.21' is 'ELESAPTMP1'.
    INFO 2008-03-29 14:37:17 DBEXPSERVER_NT_IND InternalColdKeyCheck:0
        The CD CDEXPORT1 will not be copied.
    INFO 2008-03-29 14:37:36 DBEXPORTINSTANCE_NT_IND CheckValueForKey:0
        The installation phase is starting now. Please look in the log
        file for further information about current actions.
    INFO 2008-03-29 14:37:36
        Requesting Export Details
    INFO 2008-03-29 14:37:36
        Requesting Export Details
    INFO 2008-03-29 14:37:36 DBEXPCOMMONDBENV_NT_MSS SyCoprocessCreate:931
        Creating coprocess osql.exe ...
    INFO 2008-03-29 14:37:36 DBEXPCOMMONDBENV_NT_MSS SyCoprocessExecute:171
        The process osql.exe puts out:
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS GetDbVersion:0
        Version String read from MS SQL Server: Microsoft SQL Server
        2000 - 8.00.2039 (Intel X86)       May  3 2005 23:18:38       Copyright
        (c) 1988-2003 Microsoft Corporation      Enterprise Edition on
        Windows NT 5.2 (Build 3790: Service Pack 2)
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS GetDbVersion:0
        Major Version read from MS SQL Server: 800
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS GetDbVersion:0
        Minor Version read from MS SQL Server: 2039
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS SyCoprocessCreate:931
        Creating coprocess osql.exe ...
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS SyCoprocessExecute:171
        The process osql.exe puts out:
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS InternalInstallationDo:0
        You have a correctly configured MS SQL Server with charset cp850
        and sortorder bin_cp850!
    INFO 2008-03-29 14:37:37 DBEXPCOMMONDBENV_NT_MSS InternalInstallationDo:0
    ooo MSGERR Wrong type of Parameter: area:74, id:1, typeofParam:4, char:d
    ooo MSGERR Dump of parameter with valid type:
    ooo MSGWAR MsgAreaName:SY_AREA_RI_MSGL, MsgIdName:RI_MSGL_MIN_MAJORVERSION
    ooo MSGERR --- SYLOGDATA:ParaNr: 1, Typ:4
    ooo MSGERR --- SYLOGDATA:ParaNr: 2, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 3, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 4, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 5, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 6, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 7, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 8, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 9, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr:10, Typ:1, long=0
    ooo MSGERR Wrong type of Parameter: area:74, id:1, typeofParam:4, char:d
    ooo MSGERR Dump of parameter with valid type:
    ooo MSGWAR MsgAreaName:SY_AREA_RI_MSGL, MsgIdName:RI_MSGL_MIN_MAJORVERSION
    ooo MSGERR --- SYLOGDATA:ParaNr: 1, Typ:4
    ooo MSGERR --- SYLOGDATA:ParaNr: 2, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 3, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 4, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 5, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 6, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 7, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 8, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr: 9, Typ:1, long=0
    ooo MSGERR --- SYLOGDATA:ParaNr:10, Typ:1, long=0    Your actual major version of MS SQL Server is
    INFO 2008-03-29 14:37:37
        Requesting Export-Specific Parameters
    INFO 2008-03-29 14:37:37
        Testing the Database Connect
    INFO 2008-03-29 14:37:37 DBDBSLTESTCONNECT_NT_IND InternalInstallationDo:0
        See logfile dev_dbsl for further information.
    INFO 2008-03-29 14:37:37 DBEXPSERVER_NT_IND InternalWarmKeyCheck:0
        The CD CDEXPORT1 will not be copied.
    INFO 2008-03-29 14:37:37
        Requesting Information on CD-ROMs
    INFO 2008-03-29 14:37:37
        Creating the Export Directories
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB. If it does not
        exist creating it with user NULL_POINTER, group NULL_POINTER and
        permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\ORA. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\ORA from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\INF. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\INF from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\ADA. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\ADA from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\MSS. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\MSS from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\DB2. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\DB2 from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\DB4. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\DB4 from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DB\DB6. If it does
        not exist creating it with user NULL_POINTER, group NULL_POINTER
        and permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DB\DB6 from 777 to 7.
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:353
        Checking existence of directory F:\EXPORT~2\DATA. If it does not
        exist creating it with user NULL_POINTER, group NULL_POINTER and
        permission 7 ...
    INFO 2008-03-29 14:37:37 DBEXPDIRECTORIES_NT_IND SyDirCreate:2207
        Changing permission for file F:\EXPORT~2\DATA from 777 to 7.
    INFO 2008-03-29 14:37:37
        Creating the R3load Control Files
    INFO 2008-03-29 14:37:37 R3LDCTL_NT_IND R3ldctlDo:0
        C:\Users\prdadm\Install\R3LDCTL.EXE -p C:\Users\prdadm\Install
    INFO 2008-03-29 14:37:37 R3LDCTL_NT_IND SyCoprocessCreate:931
        Creating coprocess C:\Users\prdadm\Install\R3LDCTL.EXE ...
    INFO 2008-03-29 14:37:38 R3LDCTL_NT_IND R3ldctlDo:0
        WARNING: no technical settings for table "A055" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "A056" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "A064" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "A065" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "AABLG" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "AANK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "AANL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ALQRFCMON" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ALQRFCMONA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ALQRFCMONO" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ALQRFCMONQ" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANAR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANEV" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANGA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANLH" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANLV" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANLW" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ANLX" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "APQD" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "APQI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ATAB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "B015" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "B060" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BGPROT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BKORA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BKORR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BPHIER" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BSIW" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BTCEVTJOB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BTCJSTAT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BTCOPTIONS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BTCSED" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BTCSEV" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BTCUEV" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BUXPRA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "BVOR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CATCU" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CATDB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CATL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CATM" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CBPL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CCCFINI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CD0BAS4VI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CD0BAS5VI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CD0MC5" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CD0T200TAB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CD0T210TAB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CD0TBSH001" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CDCLS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CE1S001" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CE2S001" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CE3S001" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CE4S_CP_FLAG" in SAP
        data dictionary - defaults used
        WARNING: no technical settings for table "CF003" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CF005" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CFIS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CHGRP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CKHT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CKKS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CKKT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CKPP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CKPS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CKPT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CLRK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CLU4" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CNTLREM" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "COKAA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "COOI_PI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "COSPP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CRHH" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CRID" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CRS_BLOCKS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CRVP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CSLT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CSSK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CVEP1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CVEP2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CVER1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CVER2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CVER3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "CVER4" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DD02ALL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DEBI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DELM" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DLIX" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOKALTLANG" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOKCL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOKID" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOKSH" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOKSI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOSSH" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DOSSI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYCR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYLI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYLT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYO1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYO2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYO3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DSYSX" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DVERS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DVPOOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "DVPOOLTEXT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "E070N" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EANQ" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EBSEG" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EBUB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EDFIL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EDI30C" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EDI40" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EDIDOC" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EDIE5" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EDMAP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EIPA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EKAN" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EKPB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EKUB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EPIDXB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EPIDXC" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EREF" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EREN" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "ERET" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EST07" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EST0B" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EST0D" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EST0F" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EWUCUSA2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "EWUCUSAK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FEBKEY" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FINPL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FINS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FINV" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FLAPP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FLEMP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FMCFSI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FMCOPI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FMGEBER" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FOH01" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "FREF" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GCLIENTS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLOO1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLOO2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLPO1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLPO2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLPO3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLS2CLUS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLSO1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLSO2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLSO3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLSP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLT0" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLTO1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLTO2" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLTO3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLTP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GLTPC" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GSBLCA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "GWFEODE" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "HLPNA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "HRARCENQ" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "HRMS_BIW_PPDELTA" in
        SAP data dictionary - defaults used
        WARNING: no technical settings for table "HRPMPROT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "HRPMSIM" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "HRPY_RGDIR_TEMP" in SAP
        data dictionary - defaults used
        WARNING: no technical settings for table "IMPREDOC" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "INDX" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "INETX" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "INHB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "IXDIT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "IXTYP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "IXTYT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "JVT1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "J_1AWITNR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "J_1BCBTAXPROC" in SAP
        data dictionary - defaults used
        WARNING: no technical settings for table "J_1BITEMTYPES" in SAP
        data dictionary - defaults used
        WARNING: no technical settings for table "K002" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KALK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KAPE" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KAPOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KBPOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KCPOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KDPOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KEPOOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KGPOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNAS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNB5" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNC1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNC3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNMTK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNOB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNVA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNVD" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNVI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNVL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNVS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KNVT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOCLU" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KONAIND" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOND" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KONR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTD001" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTE001" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTE002" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTE003" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTE004" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTE005" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTG002" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KOTG003" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "KRED" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LDAN" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LDKO" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LFAS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LFB5" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LFC1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LFC3" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LISA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "LISPLF" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MASE" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MAT1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MBAN" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MBMP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MBPR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MBRK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCEKS" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCLIB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCLIO" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCLIP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCLIT" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCVSRFP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MCY1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MEIK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MEIN" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MEKK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MEOR" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MHNDO" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MHNKA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MKLK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MKUB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MLIB" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MODSAP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MOFF" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MPRP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MSAK" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MSEGO1" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MSET" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MSOA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MSPOOL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "MSTA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_ADMC" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_ADRC" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_ADRP" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_AKTE" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_CF01" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_CKKA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_CLFN" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_DARL" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_DGMI" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_HORD" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_IBEW" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_IFLM" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_IIMA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_IRLM" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_J1BA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_J1IA" in SAP data
        dictionary - defaults used
        WARNING: no technical settings for table "M_J1IB" in SAP data
        dictionary - defaults used

    Hello,
    The version of perl is correct.
    Anayways i have solved the problem!
    there was problem with the DBEXPORT.R3S file. i referred a SAP note for the same.(Installation of 4.6c on windows). In this check the section for post installation activity.
    I hope this can be a input for other experts who may face such problem!!!
    Regards,
    Shridhar!!!!

  • Error in database export

    We have migrated from Oracle 6 database to Oracle 8i database. All user applications are functioning perfectly but full database/user export terminates unsuccessfully with errors. The log for the export is as under
    Connected to: Oracle8i Enterprise Edition Release 8.1.5.0.0 - Production
    With the Partitioning and Java options
    PL/SQL Release 8.1.5.0.0 - Production
    Export done in US7ASCII character set and US7ASCII NCHAR character set
    About to export specified users ...
    . exporting pre-schema procedural objects and actions
    . exporting foreign function library names for user DEEPAK
    . exporting object type definitions for user DEEPAK
    About to export DEEPAK's objects ...
    . exporting database links
    . exporting sequence numbers
    . exporting cluster definitions
    . about to export DEEPAK's tables via Conventional Path ...
    . . exporting table XX 0 rows exported
    . exporting synonyms
    EXP-00008: ORACLE error 904 encountered
    ORA-00904: invalid column name
    EXP-00000: Export terminated unsuccessfully
    Is this problem with export-import views?
    last few lines of catexp.sql in our system read as under
    REM Add versioning support for export
    REM This will get bumped up as the views evolve. The insert is needed
    REM for upgrades from 7.0 or new databases. The update is needed for
    REM databases that have older compatibility.
    REM These are the releases when the compatibility was bumped:
    REM 7.0.* - no compatibility - assume zero
    REM 7.1.3 - set to one
    REM 7.2.1 - set to two
    REM 7.2.3 - set to three
    REM 8.0.1 - set to four
    REM 8.0.2 - set to five
    REM 8.0.3 - set to six
    REM 8.0.4 - set to seven
    REM
    insert into props$
    select 'EXPORT_VIEWS_VERSION', '7', 'Export views revision #' from dual
    where not exists
    (select 'x' from props$ where name = 'EXPORT_VIEWS_VERSION')
    update props$ set value$ = 7 where name = 'EXPORT_VIEWS_VERSION'
    commit
    Does this has some bearing on the problem

    I recommend you to make that export in two parts. Export your data from Oracle 6 to Oracle 8.0.6 and after make an export with Oracle 8.0.6 to Oracle 8i because the migration can not be directly.
    [email protected]
    Joel P�rez

  • How can I share a Tiger server's User database to a Panther server?

    I need some help to set this up. Keep in mind I do not have a DNS server.
    I have a Tiger server with Xserve and an older Panther server, both on the same local network. I have a whole bunch of users setup on the Tiger server. The Panther server does not have any users setup on it. I do not want to have to type in all the users all over again in the Panther server. What I'd like to be able to do is somehow share and syncronize the user database on the Tiger server with the Panther server.
    I looked into the Open Directory settings but I do not understand what to do. How do I configure the Tiger and Panther servers respectively so the Panther server can sync with the Tiger server's users database. Is this possible? It seems like it with Open Directory, one being the Open Directory Master and the other being the Open Directory Replica? But I just don't understand how to set this up. Also the Panther OD settings seem quite different than Tiger's in Open Directory.
    Any help would be appreciated.
    Message was edited by: robocub1

    Hi
    It may be best to set up your 10.4 Server as an Open Directory Master first and then use Directory Access on your 10.3 Server to connect to the Tiger Server so as it can use the same User Database. This should be possible. OD Master/Replica relationships are not possible if the OS versions are different, even if the Master was 10.4.11 and the Replica was 10.4.10. You have no chance when its 10.4 and 10.3.
    http://images.apple.com/server/macosx/docs/OpenDirectory_Adminv10.5.pdf
    The link is for 10.5 but the basics are the same. This is a recent post that describes how to set up an OD Master:
    http://discussions.apple.com/thread.jspa?threadID=1377046&tstart=0
    I'm guessing that your 10.4 Server is Standalone and is serving simple file services only (AFP and possibly SMB/Windows). If this is the case (and I can't see how it can't be) then your users will be in the local NetInfo node. This will be the default node that is presented to you in WorkGroup Manager. You always get a warning that your are working in an invisible node (if you have not disabled this) when working in the Server's local node. Don't worry there is nothing wrong with the warning. WorkGroup Manager on Panther (10.3) Server works the same way.
    You could if you wanted to simply export the Users and Groups from WGM in 10.4 and import them into WGM on 10.3. This should save you having to key them all in again. If the prospect of configuring internal DNS Services and all that goes with it seems to much for you then this is probably the simplest option. How do you do this? Launch WGM (its the same for both versions), select the Server Menu and select Export after first selecting desired users. Do the same for Groups. Use the same procedure in reverse. The Users and Groups files are not very big and can easily be transferred using a memory stick etc.
    There are differences between the two versions which are mostly to do with Server Admin. In 10.4 Server there are more services. One of the Services will be Open Directory. In 10.4 Open Directory will only show a green light by the side of the service if it is in any role other than Standalone. Server Admin on 10.3 Server will always show the green light by the side of the Open Directory Service. This does not mean that it is an OD Master, you have to click on Settings and inspect the Role to see what it actually is.
    You should be able to connect to a 10.3 Server with 10.4's Admin tools but don't be tempted to use Server Admin to configure/change anything on the 10.3 Server. You should not be able to go the other way 10.3 > 10.4 using the same tools.
    Internal DNS Services are a requirement for LDAP Services (and pretty much everything else) on Servers generally, although for simple file services not absolutely necessary. Internal DNS Services do not have to be configured on the Server itself just as long as they are configured on another server, for example, on the same network. If these are the only two servers on the network then you will have to configure DNS Services on either one or both of them depending on what you want.
    Not available on your 10.3 Server but is on your 10.4 Server are Access Control Lists (ACLs). This is a permissions model that is in addition to the standard POSIX permissions. Think carefully about how you provide permissions to your network clients if there is a mix of client OS, 10.3, 10.4 etc.
    Hope this helps, Tony

Maybe you are looking for

  • DMS Configuration/Blue Print

    HI, We are inprocess of implementing the DMS in our organization, Pls any body can share the configuration/blue print document to mail id [email protected] Pls guide us to proceed further. if its useful, awards will be provided. Thanks in advance. Ma

  • I have a lot of tabs open and want them to open again

    when I open Firefox. Can't find that setting

  • SMIL ignores 'switch' in 'seq' tags

    I've built a player based off sprint 10 (0.93) that uses the SMILPlugin and Dynamic Streaming. The player was working great with single items, either flv or a set of MBR streams, once I started sequencing them I ran into some issues. It appears the S

  • PAL/NTSC issue

    We have a problem on our new project. The show was shot on three different camcorders. It was supposed to be Anamorphic DV-NTSC. But it looks like nobody on the shoot checked their camera settings. So now we're in a weird situation: Camera 1 (miniDV)

  • Battery time dramatically down after Leopard update

    I got my battery replaced in august 2006 (the battery exchange program). Before upgrading to Leopard I had a capacity of 4200mAh. Now with Leopard I only get 1475mAh. The computer will not even go to sleep when the battery runs out, it just shuts dow