what you think About this Information :
Smallfile tablespaces can contain up to 1024 files, but bigfile tablespaces contain only one file that can be 1024 times larger than a smallfile tablespace.
https://web.stanford.edu/dept/itss/docs/oracle/10gR2/server.102/b14220/physical.htm
It's just like Rivaldo11 said, not all tablespaces may have one or more data files! Bigfile tablespaces can only have ONE datafile (which can be and in most cases are much bigger in size than smallfile datafiles) - as stated in your statement.
A is definitely incorrect!
My picks would also be C, D and F
Nope, "Not All tablespaces might have one or more data files", this is one of question when they play with your logic and common sense, I fell into the same logic as yours, before I negate the question.
A is wrong. Because bigfile tablespaces may have only one datafile
B is wrong. Because if a tablespace has more than one datafile then the extents of the segment can be in any one or all of the data files. Remember that tablespaces are LOGICAL objects and the segment lives in the logical object, regardless of which file the extent exists on.
C is correct. Smallfile tablespaces may have many datafiles that collectively exceed the the size of the datafile that is in the bigfile tablespace
D is correct. The opposite of option B. A tablespace is a logical object made up of one or more datafiles. With locally managed tablespaces the server will decide where the next extent allocation should be done for a segment
E is wrong. A segment must have all it's extents in the same tablespace, and block size is defined at tablespace level
F is correct. If a segment has row pieces that collectively are less than or equal to the total storage requirement of one extent then the segment will have only one extent allocated to it
G is wrong. A segment can reside in one tablespace only
A C F, checked.
A is true, it say ---> one OR more
D is false.
D. A segment can span multiple data files in some tablespaces
'A segment can span one or more data files, but it cannot span multiple tablespaces'.
So in SOME tablespaces is not correct
A C F, checked.
A is true, it say ---> one OR more
D is false.
D. A segment can span multiple data files in some tablespaces
'A segment can span one or more data files, but it cannot span multiple tablespaces'.
So in SOME tablespaces is not correct
A C F
A is correct. Bigfile tablespace have only one datafile and smallfile tablespace have several datafiles.
B is wrong. The extents of a segment could reside in the some others datafiles in the same tablepsace
C is correct. The difference between smallfile tablespace and bigfile tablespace is the number of datafile. The max size of datafile is same.
D is wrong. A segment can span multiple data files in same tablespace, but not in some tablespaces
E is wrong. The block size can be defined in tablespace in creation.
F is correct.
G is wrong. Refer to D
B is wrong .
If the initial extent become full, and if more space is required, then the database automatically allocates an incremental extent for this segment. An incremental extent is a subsequent extent created for the segment.
The allocation algorithm depends on whether the tablespace is locally managed or dictionary-managed. In the locally managed case, the database searches the bitmap of a data file for adjacent free blocks. If the data file has insufficient space, then the database looks in another data file. Extents for a segment are always in the same tablespace but may be in different data files.
https://docs.oracle.com/en/database/oracle/oracle-database/19/cncpt/logical-storage-structures.html#GUID-C205981E-182A-466D-B151-090455F9ECE7
One tablespace may have multiple datafile.
A segment can be span multile datafile which reside in the same tablespace.
A extent, however, should be reside in same datafile.
So...I think the answer is B,C,AorF
A&F are ambiguous, but D&E&G are wrong.
D - A segment cannot span multiple data files in 'some' tablespaces. They should be reside in one tablespace.
reference : https://docs.oracle.com/cd/A57673_01/DOC/server/doc/SCN73/ch3.htm#extents
"... The segments also can span files, but the individual extents cannot."
Some tests said G is right ... G. Segments can span multiple tablespaces
A Segment can't span multiple tablespaces ... but the Segments, (table, Indexes,cluster,..) may be span multiple tablespaces .... it is on plural ... so may be possible correct
Hi,
B is correct.
https://docs.oracle.com/en/database/oracle/oracle-database/19/cncpt/logical-storage-structures.html#GUID-E3D8E030-A056-40AC-9B7E-8C957E28EE75
"Allocation of Extents
By default, the database allocates an initial extent for a data segment when the segment is created. An extent is always contained in one data file."
G is wrong because
Each segment belongs to one and only one tablespace. Thus, all extents for a segment are stored in the same tablespace. Within a tablespace, a segment can include extents from multiple data files, as shown in Figure 12-2. For example, one extent for a segment may be stored in users01.dbf, while another is stored in users02.dbf. A single extent can never span data files.
A segment can have several extents:
Segments
The level of logical database storage above an extent is called a segment. A segment is a set of extents that have been allocated for a specific type of data structure, and that all are stored in the same tablespace. For example, each table's data is stored in its own data segment, while each index's data is stored in its own index segment.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Rivaldo11
Highly Voted 4 years, 6 months agoama
4 years, 5 months agoadoptc94
4 years, 4 months agonyale
3 years, 4 months agoalgerianphoenix
2 years, 8 months agoFranky_T
Highly Voted 2 years, 9 months agowgenser
Most Recent 3 months, 2 weeks agoSpyderSh
1 year, 4 months agoSpyderSh
1 year, 4 months agoHell3n
1 year, 4 months agoHell3n
1 year, 4 months agolinhao
1 year, 5 months agoAliKhan345
1 year, 8 months agoj_tw
1 year, 9 months agoMinoro
2 years, 1 month agoalan_resende
2 years, 1 month agoDarkseid1231
2 years, 7 months agoAramazd
2 years, 9 months agoAramazd
2 years, 9 months agoAramazd
2 years, 9 months agoryuah
3 years ago