Master database logical file names are different - Please Help!

Today I noticed that one of the server in our environment,
when i run
SELECT *
FROM sys.database_files
i got results
data_space_id name
1 master2
0 master_Log2
Please note logical name of the master database files.
But, in SSMS if i right click and choose properties for master database, it shows logical file names are master, mastlog.
How can this be happened? How can i fix this issue and make it both same names for master database?
Please help!
Its nothing to worry about may be master was restored from backup which had logical file name as master2
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Similar Messages

HT1414 the iphone software update server could not be contacted.a duplicate file name was specified , please help as this is driving me nuts,does anyone know which file it could possibly be ?

Hi could anyone help me out? my iphone 3gs keeps restarting itself every two minutes which i think is some kind of software issue,now there are a number of things i have done starting with putting in a new battery.when i charge the phone it resets itself every two minutes or so and the battery indicator stays at 4% so i decided to restore the phone on itunes (which is the latest edition) and when i connect my phone which i have put into recovery mode using the buttons, i get an error message saying :- the iphone software update server could not be contacted.a duplicate file name was specified. i have tried re-installing i tunes and that doesn't solve the issue and i have trawled through the program files to see if i could spot the duplicate but without success ,has anyone had the same issue and resolved it?

An iPhone 3G cannot be updated beyond iOS 4.2.1...that's the end of the line for your phone.

Error - Logical file is not part of database. Use RESTORE FILELISTONLY to list the logical file names

I made a script to restore .bak or backup files. It works for some databases, but not for one. How do I make it work for any type of .bak file ? This is in sql server 2008. The error message is -
Msg 3234, Level 16, State 1, Line 1
Logical file 'Northwind_Data' is not part of database 'Northwind'.
Use RESTORE FILELISTONLY to list the logical file names.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
Script -
IF DB_ID('Northwind') IS NULL
BEGIN
RESTORE DATABASE [Northwind]
FILE = N'Northwind_Data'
FROM
DISK = N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SS2008\MSSQL\Backup\Northwind.bak'
WITH FILE = 1,
MOVE N'Northwind_Data'
TO N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SS2008\MSSQL\DATA\Northwind.mdf',
MOVE N'Northwind_Log'
TO N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SS2008\MSSQL\DATA\Northwind_0.LDF',
NOUNLOAD, STATS = 10
END

Hello,
The issue you are facing might be related to below link
http://support.microsoft.com/kb/2487231/en-us
As per link this is known issue.Can you please check service pack level of SQL Server 2008 .It should be SP3.Please apply SP3 and see if the error subsides.
Also error suggests logical file name 1 which you are giving is not part of the backup set from which you are trying to restore.You should first use below query to determine right file then proceed with restoration of the same.
restore filelistonly from disk='C:\Program Files\Microsoft SQL Server\MSSQL10_50.SS2008\MSSQL\Backup\Northwind.bak'
if file ID is 3 may be your restore script would be like below
F DB_ID('Northwind') IS NULL
BEGIN
RESTORE DATABASE [Northwind]
FILE = N'Northwind_Data'
FROM
DISK = N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SS2008\MSSQL\Backup\Northwind.bak'
WITH FILE = 3,
MOVE N'Northwind_Data'
TO N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SS2008\MSSQL\DATA\Northwind.mdf',
MOVE N'Northwind_Log'
TO N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SS2008\MSSQL\DATA\Northwind_0.LDF',
NOUNLOAD, STATS = 10
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

How to creat the logical file name.

Hello All,
I want to create Logical file name in my program, So Please guide me in this issue.
Thanks

Check this out
http://help.sap.com/saphelp_45b/helpdata/en/2a/fa02b7493111d182b70000e829fbfe/content.htm
FU FILE_GET_NAME
Text
Assign the Physical File Name Using a Logical File Name
Functionality
R/3 applications run on various platforms with various file systems. This function module enables you to use platform-independent logical file names in your application programs.
Based on definitions maintained in customizing tables for platform-independent file names, the function module converts a logical file name to the corresponding physical file name and path for the hardware platform concerned.
For this conversion to work for different platforms, the definition of a logical file name must include a logical file path, which in turn is converted to different physical file paths, depending on the particular platform. The platform-specific file name returned by the function module is composed of the physical file path for the current platform and the physical file name associated with the logical file name. Placeholders in physical file and path names are substituted at runtime by the corresponding current values.
Example
logical file name: MONTHLY_SALES_FILE
physical file name: VALUES<PARAM_1>
logical path: SALES_DATA_PATH
physical path (UNIX): /usr/<SYSID>/<FILENAME>
physical path (Windows): C:\SALES\<FILENAME>
Example 1
Get file name for UNIX platform
(current system: K11)
CALL FUNCTION 'FILE_GET_NAME'
EXPORTING
LOGICAL_FILENAME = 'MONTHLY_SALES_FILE'
IMPORTING
FILE_NAME = FILE
FILE_FORMAT = FORMAT.
Result:
FILE = /usr/K11/VALUES
FORMAT = WK1
Example 2
Get file name for UNIX platform, passing a parameter
(current system: K11)
CALL FUNCTION 'FILE_GET_NAME'
EXPORTING
LOGICAL_FILENAME = 'MONTHLY_SALES_FILE'
PARAMETER_1 = '_TST'
IMPORTING
FILE_NAME = FILE
FILE_FORMAT = FORMAT.
Result:
FILE = /usr/K11/VALUES_TST
FORMAT = WK1
Example 3
Get file name for WINDOWS platform, with file name extension
CALL FUNCTION 'FILE_GET_NAME'
EXPORTING
LOGICAL_FILENAME = 'MONTHLY_SALES_FILE'
WITH_FILE_EXTENSION = 'X'
IMPORTING
FILE_NAME = FILE
FILE_FORMAT = FORMAT.
Result:
FILE = C:\SALES\VALUES.WK1
FORMAT = WK1
Notes
All definitions needed for the platform-independent assignment of file names are maintained client-independently with transaction FILE. Logical file names (but not logical file paths) can also be defined specifically for the current client with transaction SF01. Transaction SF07 generates a list of current definitions.
The following concepts are used in the platform-independent assignment of file names:
Logical file name
A descriptive name for a file which is associated with these values:
physical file name
file format
logical file path.
If no logical file path is specified, the function module returns the physical file name only; placeholders are substituted by current values.
Physical file name
The physical file name may contain placeholders.
Logical file path
A descriptive name for a path which is associated with these values:
syntax groups (groups of operating systems)
physical file paths.
Physical file path
The physical file path is defined for a particular syntax group. It must contain the reserved word <FILENAME> as a placeholder for the file name. It may also contain other placeholders.
Operating system
Presentation server and application server can run under different operating systems. The current value for the application server can be obtained from the system field SY-OPSYS, the value for the presentation server by calling function module WS_QUERY.
Both operating systems must be defined and assigned to a syntax group.
Syntax group
Group of operating systems with a common syntax for file and path names (e.g. HP-UX and SINIX).
Placeholder
Reserved words, set in angle brackets, which can be included in physical file and path names (e.g. <DATE>, <FILENAME>). You can find information on possible reserved words in the online help (F1 help) for the fields physical file name and physical file path when maintaining platform-independent file names with transaction FILE.
If the logical path associated with a logical file name does not specify a physical path for the current operating system (syntax group), the path stored in the profile parameter DIR_GLOBAL of the current system is used for generating a complete platform-specific file name.
Parameters
CLIENT
LOGICAL_FILENAME
OPERATING_SYSTEM
PARAMETER_1
PARAMETER_2
PARAMETER_3
USE_PRESENTATION_SERVER
WITH_FILE_EXTENSION
USE_BUFFER
ELEMINATE_BLANKS
EMERGENCY_FLAG
FILE_FORMAT
FILE_NAME
Exceptions
FILE_NOT_FOUND
Function Group
SFIL
Thanks
mahesh

Archiving : Change of Logical File Name & physical path

Hello friends,
We are doing archiving for a Z* archiving object.
We run a write job(not delete job till now) for this archiving object and it created archive files in .../SYS/GLOBAL directory as was expected from settings of Logical File Name and hence physical path corresponding to it. So far no problem..
Now, requirement is to change this path and for this i created a new Logical File Name with a different physical path.
My concern is, about already archived data in older path. Should i only run delete job for that session ?
Or should i copy the archive files to new path and then start delete job OR do a write job once again..
please suggest.
thanks
ashish

Hello Juan,
Ok, i can copy the files, those are not too many as we did it only for 2 months selection.
Can i go for write job again for same selection ? If yes, probably it will create a new session.. correct ? and then i will go for deletion for new session.
If this is also correct way, i want to do this.. as till now this has been one for only 2 months and we are going to do for 8 yrs.
One more question, will the be any problem for having 2 sessions for same selection.. means 2 write or archive job for same selection.
thanks
ashish

OHD - Logical File Name

Hello all,
I have a question about using a logical file name in an OHD (BI 7.0). Because we need to transport the OHD to a different server, we cannot use the File option in defining the OHD. We need to use the option, Logical File. In t-Code FILE, we cannot seem to create a physical path that the OHD recognizes.
This is the path in AL11 where we want the file to end up: /usr/sap/BIP/DVEBMGS17/work/GGLF010.CSV with a server of prdsap01. We are creating the OHD in a different system with a different server and path. How should the physical path (mapped to the logical path) be defined. I know we have to use <FILENAME> to represent the OHD output file (GGLF010). What variables do we use for the rest of the path? Do the variables have to be specifically defined or are they delivered by SAP?
Any help would be greatly appreciated!
Sheila

I don't know if this is relevant to this issue, but seems related.
When using OHD I noticed that two files are produced, the data file and the header file, unfortunatly when writing to the application server the file names output are identical. Therefore the header file overwrites the data file - anyone else experience this???
It is not possible to do anything about this using FILE settings so as a workaround (becasue I couldn't find/ an OSS note) I modified the standard class to ensure the data and header files names were unique:
METHOD: DETERMINE_FILENAME of class CL_RSB_FILE_GENERAL
o_filename_ctrl = l_filename.
*{ INSERT
*SAP BUG RENAMING HEADER FILE ELSE DUPLICATE FILES WILL OCCUR!!!
REPLACE '.CSV' IN o_filename_ctrl with '_HDR.CSV'.
*} INSERT
clear n_requid_current.
endmethod.
This assumes that the file output has .CSV as a file extension. This worked and now I get both the header and the data file.
If anyone could let me know if you have experienced this and how you resolved it would be nice.
cheers,
Asep

Logical file name transport

Hi Friends,
I have created logical path and logical file name using FILE Transaction code, the problem was logical Path was saved in transport request and logical file name not saved in Transport request, Could you please help me logical file name save are not in the transport request.
Thanks in advance,
Jayachandran.A

Run transaction FILE, in the menu goto "Table view", "transport", select or create a transport request. In node "logical file name definition, cross client", select your file names and in the menu bar click on "include in request"
Regards,
Raymond

Mapping physical file name to logical file name

Hi All,
Can anybody let me know wht is the procedure to map a logical file name to physical file name. wht is the use of logical file name when there exists physical file name?
Thanx in Advance

As far as creating the Logical path its done through the transaction code file by using options
Steps are:
1. Logical file path definition which is logical file path name.
2. Assignment of physical path to logical path - where we give the physical path to the logical path name defined in the last step.
After creating the Logical path the procedure to attach the file name to the Logical path is as follows:
Use the function Module C13Z_FRONT_END_TO_APPL to upload the file from the front end to the application server.
Source file on front end will be the CSV file path which is to be uploaded to the application server
Target file on application server will be the physical path of the file on the application server where the file is to be uploaded.
Attach the physical path of the file on the application server to the Logical file using transaction code file.
Logical File: The Logical name of the file which will be used by the interfaces to upload the file
Physical file: The name of the physical file on the application server
Logical path: The path of the physical file on the application server where it is stored.
The possible reason for the use of Logical file name could be we can have directories within SAP in which we can have logical files stored. These files can be used by various interfaces. Different Logical paths can be used for different interfaces. the second reson can be to give more user friendly name to the file rather than a long physical name to the file.

Logical File names for OHS

Hi all,
I wanted to create the files names dynamically
I know we can use transaction file and define a logical name with variables and assign value sto the variables to get the physical name.
my requirement is to fetch different values for the variables as well. for example : let ssay I have to create two data files using a process chain . both should have same time stamp at the end of the file.
I 'm planning to store this timestamp in a table. so during run time I want FILEname1_timestamp and Filename2_timestamp.
wher etimestamp is the same value for both files. but the prefix is different.
please let me know a optimum way to create this in BI7.0

I store this as a variable in PARAMVALUE table and us ethis in the logical file name of the File in transaction FILE.

Get logical file name

Hi Gurus,
I know the physical path of a file. Can anyone tell me how do I view this file? I do not know the logical file name, hence cannot use AL11 to view the file.
Regards,
Rishi

Hi,
There are some function modules, Can you please check:
FILE_GET_NAME_USING_PATH : Generate a complete file name with file name and logical path
FILE_GET_NAME : Assign the Physical File Name Using a Logical File Name
FILE_GET_NAME_AND_LOGICAL_PATH: Assign physical file names and get logical path
Below link also helpfull.
[http://help.sap.com/saphelp_nw04/helpdata/EN/8d/3e4ec2462a11d189000000e8323d3a/frameset.htm]
Regrads,
Lokesh.
Edited by: Lokesh Tarey on Apr 20, 2010 12:53 PM

I have a few hundred duplicates in my iPhoto library, but the file sizes are different. So one is 1.3mb and one is 567kb. I want to delete the smaller ones, but short of comparing each duplicate, is there a way to do this?

I have a few hundred duplicates in my iPhoto library, but the file sizes are different. So one is 1.3mb and one is 567kb. I want to delete the smaller ones, but short of comparing each duplicate, is there a way to do this? I've been looking at Duplicate Annhilator but I don't think it can do it.
Thanks!

I just ran a test with iPhoto Library Manager, Duplicate Annihilator, iPhoto Duplicate Cleaner, Duplifinder and Photodedupo. I imported a folder of 5 photos into a test library 3 times, allowing iPhoto to import duplicates. I then ran the 5 photos thru resizer to reduce their jpeg compression but all other aspects of the file the same.
None of the duplicate removal apps found set that was reduced in the file resizer. That's probably due to the fact that the file creation date was being used as a criteria and the resized photo would have a different file creation date even though the Image Capture date was the same.
They all found the 3 regular duplicates and some of them would mark two and leave the 3rd unmarked. iPhoto Duplicate Cleaner can sort the found duplicates by file size but if the file was edited to get the reduced file size it might not be found as it would have a different file creation/modification date.
iPhoto Library Manage was able to find all duplicates and mark them as such if the file names were the same the the filename option was selected. Otherwise it also missed the modified, resized version. It allowed one to select the one photo to save before going to work on the library.
So if a photo has been reduced in image quality or pixel size it will not be considered a duplicate.
OT

In LSMW while executing the specify file step logical file name and path.

Hi ,
In LSMW , while executing the specify file step, logical file name and path is mandatory field to entry, but in some of other LSMW objects, these fields are not mandatory one, i want to know is it possible for me to do hide the logical file name and path field in specify file step.
thanks
Md nisar

Hi,
For some Transactions while executing the Specify file step Logical File and Logical Path are mandatory.
In this case Converted file will be stored in the application server. According to the specified Logical File and Logical path.
Hope this will help you....
Regards,
Tirumala Reddy

Information about file Id, Logical file name and Physical file name

Hi All,
I am testing one program. Selection screen has 3 parameters, File Id, Logical File Name and Physical file name. In Physical File name, i am giving complete file name with path. But it is giving error. Please tell me, what is File id and what all information i need to enter for logical file name and physical file name.
Thanks
Puneet Aggarwal

hi,
try using this for filename.
parameters : p_file like rlgrap-filename.
Thanks,
Gaurav

Logical file name or logical path name incorrectly defined

Dear All,
We are doing archival in our IDES for test purpose before we do it to our Production.
Steps Performed
Copied AM_ASSET archive object to ZAM_ASSET
Logical Path
Logical path    ZAM_ASSET
Name            Asset
Syntax group    UNIX       Unix compatible
Physical path   /archive/test/<FILENAME>
Logical File Name
   Logical file    ZAMASSET
   Name            Asset
   Physical file   FI_<MONTH>_<DAY>.txt
   Data format     ASC
   Applicat.area   AM
   Logical path    ZAM_ASSET
But when we run the WRITE though SARA , in the job log we get the following
Logical file name or logical path name incorrectly defined
When generating a file name for an archive file that is to be created, the system determined that the logical file name FIAA_ARCHIVE_DATA_FILE or the logical path name ARCHIVE_GLOBAL_PATH was defined incorrectly.
But we have maintained a Logical name ZAMASSET , so we are unable to change the location of archived file and as well as the format.
So is there any setting we need to maintain apart from the logical file name and logical file path.
Suggestions are highly appreciated.
Thanks in anticipation

hi,
follow this steps :
- transaction SARA
- enter authorization objects, eg SD_VBAK
- hit button CUSTOMIZING
- Archiving Object-Specific Customizing: execute Technical Setting
- field Logical File Name enter or select ARCHIVE_DATA_FILE
- leave CONTENT REPOSITORY as blank if you are not using 3rd party for storing (eg. IBM Tivoli)
- back to customizing
- from Basis Customizing, execute : Cross-Client File Names/Paths
- on Logical FIle Path Definition, highlight (select) ARCHIVE_GLOBAL_PATH on the right pane
- double click on the Assignment of Physical Paths to Logical Path on the left pane
- double click on OS used, eg. UNIX, define Physical Path where archive file (on WRITE process) will be stored
- save changes made
- double click Logical File Definition, Cross Client on the left pane
- double click ARCHIVE_DATA_FILE on the right pane
- make sure that logical path is already set to ARCHIVE_GLOBAL_PATH
- save changes made
this setting also can be done using transaction FILE
we have experienced on this case using SAP standard archiving (SARA, SARI) and everything is fine with this setting above.
hope it help you.
rgds,
Alfonsus Guritno

Logical File name

I am getting data from a flat file and want to know how to create a logical file name instead of hard-coding the path.
Please help

Hi,
you can create logical file name in transaction SF01..
Hope it helps ,
Ravi

Master database logical file names are different - Please Help!

Similar Messages

Maybe you are looking for