BlackFriday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

SAP Exam C_TADM70_21 Topic 3 Question 84 Discussion

Actual exam question for SAP's C_TADM70_21 exam
Question #: 84
Topic #: 3
[All C_TADM70_21 Questions]

During a system copy to oracle, a table was created in the incorrect tablespace. The data class setting in *.STR file is correct and the data class/tablespace mapping in the *.TPL files is also correct. Which file type do you check for errors?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Marti at Mar 09, 2024, 07:47 PM

Limited Time Offer

25%

Off

Get Premium C_TADM70_21 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Elbert
5 months ago
Hold up, is this a trick question? I mean, the *.EXT file seems like the obvious choice, but I'm gonna double-check the other options just in case. Can't be too careful, you know?
upvoted 0 times
Deangelo
4 months ago
Yeah, I agree. Let's check the other options just to be sure.
upvoted 0 times
...
Nakita
4 months ago
I think it's the *.EXT file, that's where the tablespace information is stored.
upvoted 0 times
...
...
Lillian
5 months ago
That's a good point, Lashandra. We should make sure the table creation script is correct as well.
upvoted 0 times
...
Lashandra
5 months ago
But shouldn't we also double check the *.SQL file for any errors in table creation?
upvoted 0 times
...
Catarina
5 months ago
The *.EXT file, of course! What else would it be? This is a classic Oracle system copy scenario. I bet the person who wrote this question is laughing at us struggling with such an easy one.
upvoted 0 times
Sheron
4 months ago
Exactly, the *.EXT file is the one we should be looking at. It's a common mistake in system copies.
upvoted 0 times
...
Carlee
4 months ago
You're right, it's the *.EXT file. That's where we need to check for errors in this case.
upvoted 0 times
...
Gilbert
4 months ago
D) *.TOC
upvoted 0 times
...
Stevie
4 months ago
C) *.EXT
upvoted 0 times
...
Deeanna
4 months ago
B) *.TSK
upvoted 0 times
...
Karina
4 months ago
A) *.SQL
upvoted 0 times
...
...
Wade
5 months ago
I agree with Lillian. The *.TSK file contains the tablespace mapping information.
upvoted 0 times
...
Timothy
5 months ago
I'm a bit stumped on this one. Maybe I need to brush up on my system copy troubleshooting skills. But the *.EXT file sounds like a good place to start.
upvoted 0 times
Arlette
4 months ago
If the tablespace mapping is correct, maybe the issue lies in the *.SQL file. It's worth checking.
upvoted 0 times
...
Joanna
4 months ago
I would also suggest looking into the *.TSK file just to be thorough.
upvoted 0 times
...
Augustine
4 months ago
I think you're on the right track. Checking the *.EXT file is a good idea.
upvoted 0 times
...
Lachelle
4 months ago
I think checking the *.EXT file is a good idea. It might help identify the issue.
upvoted 0 times
...
Belen
5 months ago
No, I haven't. I'll take a look at that.
upvoted 0 times
...
Jerry
5 months ago
Have you checked the *.EXT file for errors?
upvoted 0 times
...
...
Lillian
5 months ago
I think we should check the *.TSK file for errors.
upvoted 0 times
...
Kristian
5 months ago
I think we should also double-check the *.EXT file just to be thorough. It might provide some clues as well.
upvoted 0 times
...
Leonida
5 months ago
I agree with Renay, let's check the *.TSK file first and see if there are any errors.
upvoted 0 times
...
Devon
5 months ago
Nice, the *.EXT file is the one to check. That's where the actual table creation and data transfer happen, so any issues would likely be reflected there.
upvoted 0 times
Jacqueline
4 months ago
Yes, the *.EXT file is where you would find the errors related to table creation and data transfer.
upvoted 0 times
...
Cyndy
4 months ago
Checking the *.EXT file is crucial in this situation.
upvoted 0 times
...
Kiley
4 months ago
D) *.TOC
upvoted 0 times
...
Margart
4 months ago
C) *.EXT
upvoted 0 times
...
Leonora
4 months ago
Make sure to review the *.EXT file for any discrepancies.
upvoted 0 times
...
Rasheeda
4 months ago
Yes, the *.EXT file is where you can find errors related to table creation and data transfer.
upvoted 0 times
...
Effie
4 months ago
Checking the *.EXT file is crucial in this situation.
upvoted 0 times
...
Dell
4 months ago
D) *.TOC
upvoted 0 times
...
Fernanda
4 months ago
B) *.TSK
upvoted 0 times
...
Tequila
5 months ago
A) *.SQL
upvoted 0 times
...
Mable
5 months ago
C) *.EXT
upvoted 0 times
...
Mike
5 months ago
Yes, the *.EXT file is where the table creation and data transfer happen.
upvoted 0 times
...
Shaunna
5 months ago
B) *.TSK
upvoted 0 times
...
Sabine
5 months ago
Check the *.EXT file for errors.
upvoted 0 times
...
Karima
5 months ago
A) *.SQL
upvoted 0 times
...
...
Ira
6 months ago
But the data class setting in the *.STR file is correct, so maybe the issue lies elsewhere.
upvoted 0 times
...
Denae
6 months ago
Hmm, the data class settings and mapping are correct, so it's probably not an issue with the table creation itself. I'd check the *.EXT file for any potential errors during the system copy process.
upvoted 0 times
Celia
5 months ago
Good point, let's make sure everything matches up there too.
upvoted 0 times
...
Val
5 months ago
Should we also double-check the data class setting in the *.STR file?
upvoted 0 times
...
Dorothy
5 months ago
It's possible, let's verify that first.
upvoted 0 times
...
Isaiah
5 months ago
Maybe there was a mistake in the tablespace information in that file.
upvoted 0 times
...
Mike
6 months ago
Agreed, that's the best place to start looking.
upvoted 0 times
...
Sherell
6 months ago
I would check the *.EXT file for errors.
upvoted 0 times
...
...
Renay
6 months ago
No, I believe we should check the *.TSK file. It usually holds the information we need.
upvoted 0 times
...
Ira
6 months ago
I think we need to check the *.SQL file.
upvoted 0 times
...

Save Cancel